agentleFS
Sign inStart free
wtsi-hgiwtsi-hgi/agentskills/skills/nextjs-fastapi-implementor/SKILL.md

nextjs-fastapi-implementor

Skill1 starsChanged 39 days agoMITView on GitHub

Full-stack TDD implementation for Next.js 16 + FastAPI projects. References implementation-principles, nextjs-fastapi-conventions, testing-principles, and agent-conduct. Launched as a clean-context subagent by orchestrator, bugfix, or pr-reviewer.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read and follow agent-conduct, implementation-principles,

    line 8
  2. Very specific:

    When adding/modifying an endpoint, follow the contract flow from nextjs-fastapi-conventions: Pydantic, then Zod, then contract test, then …

    line 34
  3. Distinctive:

    Ensure both schemas agree on field names, types, and constraints.

    line 37

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Next.js + FastAPI Implementor Skill

Read and follow agent-conduct, implementation-principles, testing-principles, and nextjs-fastapi-conventions before starting.

You are an implementation subagent with clean context. Read the spec and the files named in your brief; do not assume anything from a prior conversation.

Stack-Specific TDD Steps

Backend (Python)

  • Tests: pytest + httpx AsyncClient + ASGITransport in backend/tests/.
  • Targeted test: cd backend && python -m pytest tests/ -v -k <test_name>
  • Lint with: cd backend && ruff check --fix . && ruff format .

Frontend (TypeScript)

  • Tests: Vitest in frontend/tests/.
  • For visual styling changes, write a failing Playwright/perceptual test when jsdom cannot prove the user-visible result.
  • Test command: cd frontend && pnpm test
  • Lint with: cd frontend && pnpm lint && pnpm format

Contract Tests

When adding/modifying an endpoint, follow the contract flow from nextjs-fastapi-conventions: Pydantic, then Zod, then contract test, then backendJson(). Ensure both schemas agree on field names, types, and constraints.

Frontend Design

For UI tasks, also read and follow the frontend-design skill. For Tailwind v4 theming and perceptual UI tests, follow the styling/testing rules in nextjs-fastapi-conventions before changing selectors or tokens.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free