When to Use
- Starting any new feature, component, or module in Bitlysis
- Before refactoring existing code
- When the agent needs to confirm stack versions, naming conventions, or quality gates
- When routing to a specialist agent persona
Instructions
Step 1: Validate Context
Always check these files before making substantive edits:
.cursor/tech-stack.md— confirm runtime versions, framework, package manager, and Primary archetype.cursor/.agents/AGENT.md§18 — read the archetype-specific guidance.cursor/.docs/docs.md— understand the current architecture and decisions
Step 2: Confirm Stack
| Layer | Technology | Version |
|---|---|---|
| Runtime | Node.js | ≥ 22 |
| Frontend | Next.js + React + Tailwind | 15.2.x / 19 / 4 |
| Backend | FastAPI + Python | ≥ 3.11, uvicorn |
| Package manager | pnpm / pip + uv | pnpm 9.x |
| R analysis | R + renv | 4.4.x |
| Testing | Vitest + pytest | latest stable |
| Linting | Biome (JS) + Ruff + mypy (Python) | latest |
Step 3: Apply Naming Conventions
| Type | Convention | Example |
|---|---|---|
| Variables/functions (TS) | camelCase | getUserById, isLoading |
| Variables/functions (Python) | snake_case | get_user_by_id, is_loading |
| Constants | SCREAMING_SNAKE | MAX_RETRY_COUNT |
| Components | PascalCase | DataTable, UserCard |
| Files/directories | kebab-case | user-service.ts, data-pipeline/ |
| Event handlers | handle prefix | handleSubmit, handleRowClick |
| Booleans | is/has/can prefix | isValid, hasPermission |
Step 4: Code Quality Checklist
Before completing any task:
- TypeScript:
strict: true, noany, Zod 4+ for runtime validation - Python: type hints everywhere, Pydantic 2.12+,
ruff+mypy strict - Tests written alongside new features (not as an afterthought)
- No hardcoded secrets or API keys
- Conventional Commit format:
feat(scope): description - Quality gates pass:
# JavaScript/TypeScript
pnpm install && pnpm lint:web && pnpm build:web
# Python
cd services/api && pip install -e ".[dev]" && ruff check app tests scripts && pytest tests -q
Step 5: Route to Specialist (if needed)
| Task type | Persona to activate |
|---|---|
| Full-stack feature | @.cursor/.agents/.agents/fullstack-developer.md |
| R/data analysis | @.cursor/.agents/.agents/data-analyst-r.md |
| Security review | @.cursor/.agents/.agents/security-auditor.md |
| Test coverage | @.cursor/.agents/.agents/qa-engineer.md |
| UI/UX component | @.cursor/.agents/.agents/uiux-designer.md |
| Architecture decision | @.cursor/.agents/.agents/principal-engineer.md |
| LLM/agent feature | @.cursor/.agents/.agents/ai-agent-engineer.md |
| CI/CD, Docker | @.cursor/.agents/.agents/devinfra-engineer.md |
Output Format
Confirm stack, archetype, and any relevant conventions before proceeding with the task.