mcpField
F
fullstack-software-engineer

fullstack-software-engineer

github.com/rade-nugrohoDevelopment1238 installsUpdated 23w ago
Repository

About fullstack-software-engineer

A full-stack software engineering skill for delivering work across UI, APIs, and persistence. It supports vertical features, cross-client/server bug fixes, testing, and production debugging.

Key features

  1. 01Deliver features across UI and server
  2. 02Design API and database changes
  3. 03Implement auth, validation, and data flows
  4. 04Write unit, integration, and end-to-end tests
  5. 05Debug production issues and add regression tests

Use cases

  1. 01Build a vertical feature with UI, API, and storage
  2. 02Fix bugs spanning client and server
  3. 03Add authentication, pagination, or file uploads
  4. 04Test critical paths and prepare small changes

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/rade-nugroho/agentic-enteprises-skill --skill fullstack-software-engineer

After installing, type/fullstack-software-engineerin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
api_and_database.md
feature_delivery.md
frontend_integration.md
testing_debugging.md

Details

From the project README

Full Stack Software Engineer

When to Use

  • Implement a vertical feature (UI + API + persistence)
  • Design or change an API consumed by the frontend
  • Fix bugs spanning client and server
  • Add auth, validation, pagination, or file upload flows
  • Write or extend unit, integration, and critical-path e2e tests

When NOT to Use

  • Pipeline, GitOps, or cluster operations → devops or platform-engineer
  • Terraform, networking, or K8s cluster design → infrastructure-engineer
  • Security program, audit evidence, or SOC work → cybersecurity, compliance-engineer
  • Deep service architecture RFCs across many teams → senior-software-engineer
  • Explicit senior full-stack leadership scope → senior-fullstack-developer

Related skills

NeedSkill
Senior slice delivery and deeper review barsenior-fullstack-developer
RFCs and cross-service designsenior-software-engineer
Deploy and observability plumbingdevops
Requirements and acceptance criteriabusiness-analyst
User-facing docstech-writer-researcher
Front-end-only architecture and a11ysenior-frontend-software-engineer
Web sessions, CSRF, CORS, hybrid renderingweb-application-developer
Customer ticket repro and escalationsupport-engineer

Core Workflows

1. Vertical feature delivery
  1. Confirm acceptance criteria and edge cases (empty, error, permissions)
  2. Define API contract and UI states
  3. Implement server: validation, authz, persistence, migrations
  4. Implement client against typed contract
  5. Test: unit (logic), integration (API), e2e (happy path)
  6. Add logging/metrics on new paths; feature flag if risky

See references/feature_delivery.md for checklist.

2. API and database
ConcernDefault
ValidationSchema at boundary (Zod, Pydantic)
AuthSession or JWT; check authz per resource
QueriesAvoid N+1; index for access patterns
MutationsTransactions where needed; idempotency keys for payments-like flows
ErrorsStable codes; no internal details to clients

See references/api_and_database.md for pagination and migrations.

3. Frontend integration
  • Match loading/error/empty states to design
  • Prefer server fetch for read-heavy pages when using Next.js App Router
  • Client components only for interactivity
  • Accessible forms (labels, focus, keyboard)

See references/frontend_integration.md for forms and caching.

4. Testing and PR hygiene
  • Lint and typecheck clean
  • Tests cover changed behavior, not only happy path
  • No secrets in repo; env via configuration
  • Small PRs; describe rollout and rollback

See references/testing_debugging.md for test pyramid.

5. Production debugging
  1. Reproduce with correlation ID or request ID
  2. Check deploys, flags, and recent config changes
  3. Trace: logs → metrics → DB slow queries
  4. Fix with regression test; hotfix or rollback per severity

See references/testing_debugging.md for common failures.

When to load references

  • Feature flow → references/feature_delivery.md
  • APIs and DB → references/api_and_database.md
  • UI integration → references/frontend_integration.md
  • Tests and prod issues → references/testing_debugging.md

Comments

Markdown supported