agentleFS
Sign inStart free
theinternetitheinterneti/TTA.dev/.github/skills/feature-development/SKILL.md

Feature Development

Skill0 starsChanged 7 months agoMITView on GitHub

Full-stack feature development workflow from API to UI with testing

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write unit tests (AAA pattern, 100% coverage)

    line 22
  2. Distinctive:

    Document API in Logseq

    line 24
  3. Distinctive:

    Write Playwright E2E tests

    line 58
  4. Distinctive:

    Run accessibility validation (WCAG AA)

    line 59

≈ “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

Feature Development Skill

Overview

Orchestrates Backend Engineer → Frontend Engineer → Testing Specialist for complete full-stack features.

Duration: 4-6 hours (full feature) Personas Required: 3 (Backend, Frontend, Testing)

Workflow Stages

Stage 1: API Development (@backend-engineer)

Steps:

  1. Design API contract (endpoints, models)
  2. Implement FastAPI endpoints with Pydantic models
  3. Write unit tests (AAA pattern, 100% coverage)
  4. Generate OpenAPI schema
  5. Document API in Logseq

Deliverables:

  • Working REST API endpoints
  • Complete test suite
  • OpenAPI schema for frontend
  • API documentation

Handoff: Share API contract with frontend engineer

Stage 2: UI Implementation (@frontend-engineer)

Steps:

  1. Retrieve API contract from backend
  2. Generate TypeScript types from OpenAPI
  3. Create React components
  4. Implement state management
  5. Write component tests

Deliverables:

  • Functional UI components
  • Type-safe API integration
  • React Testing Library tests
  • Responsive design

Handoff: Notify testing specialist UI is ready

Stage 3: E2E Validation (@testing-specialist)

Steps:

  1. Write Playwright E2E tests
  2. Run accessibility validation (WCAG AA)
  3. Execute integration tests
  4. Perform quality gate review

Deliverables:

  • Comprehensive E2E test coverage
  • Accessibility compliance verification
  • Quality gate approval

Success Criteria:

  • ✅ All backend tests pass
  • ✅ All frontend tests pass
  • ✅ E2E tests cover user flows
  • ✅ Accessibility violations = 0
  • ✅ Integration tests validate full stack

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