api-development
API development workflow and best practices for career_ios_backend FastAPI project. Automatically invoked when user wants to develop, test, or debug API endpoints. Trigger keywords: "API", "endpoint", "route", "FastAPI", "Swagger", "console.html", "測試 API", "API 開發", "端點" Covers development flow, testing requirements, and console integration.
npx skills add majiayu000/claude-skill-registry --skill api-development-youngger9765-career-ios-backend --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# API Development Skill ## Purpose Guide API development workflow for the career_ios_backend FastAPI project, ensuring all console.html APIs are properly tested and functional. ## Automatic Activation This skill is AUTOMATICALLY activated when user mentions: - ✅ "develop API" / "API 開發" - ✅ "create endpoint" / "創建端點" - ✅ "test API" / "測試 API" - ✅ "console.html" - ✅ "Swagger UI" - ✅ "FastAPI route" --- ## Development Flow (Prototype Speed-First) ### Standard Workflow ``` 1. Write Feature Code (AI-Assisted) ↓ 70% time 2. Manual Test API (Swagger UI or Console) ↓ Quick verification 3. Write Integration Test (Verify API works) ↓ 20% time 4. ruff check --fix (Auto-fix formatting) ↓ Auto 5. Commit (Pre-commit hooks) ↓ ~5s 6. Push → CI runs Integration Tests ↓ ~2 min ``` ### Time Allocation - **Development**: 70% of time - **Testing**: 20% of time - **Fixing/Refactoring**: 10% of time **Philosophy**: Prototype phase prioritizes speed over perfection. Functional validation comes before quality optimization. --- ## Testing Requirements ### Integration Tests (Mandatory) **CRITICAL**: All `console.html` APIs MUST have integration tests. ```bash # Daily development: Run integration tests only
- Purpose
- Automatic Activation
- Development Flow (Prototype Speed-First)
- Standard Workflow
- Time Allocation
- Testing Requirements
- Integration Tests (Mandatory)
- Current Test Coverage
- Requirements by Endpoint
- Console API Verification
- All Console.html APIs Must Be Tested
- When Adding New Console Feature
- API Structure (FastAPI)
- Project Layout
Daily development: Run integration tests only poetry run pytest tests/integration/ -v Full test suite (optional during development) poetry run pytest tests/ -v Test specific API poetry run pytest tests/integration/test_auth_api.py -v Verify test coverage poetry run pytest tests/integration/ -v | grep -E "(test_.*_api\.py|PASSED|FAILED)" Current coverage (106+ tests): Start development server
What does the api-development skill do?
API development workflow and best practices for career_ios_backend FastAPI project. Automatically invoked when user wants to develop, test, or debug API endpoints. Trigger keywords: "API", "endpoint", "route", "FastAPI", "Swagger", "console.html", "測試 API", "API 開發", "端點" Covers development flow, testing requirements, and console integration.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill api-development-youngger9765-career-ios-backend --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.