senior-fullstack · sickn33 — Claude Code skill: full-stack coordination
This skill guides implementation of features spanning interface, backend, database and deployment. It verifies coherence from request through authorization to data access and response handling.
npx skills add sickn33/agentic-awesome-skills --skill senior-fullstack -a claude-codeWhat senior-fullstack does
Use senior-fullstack when building features that cross layer boundaries: browser, service, storage. The skill starts by inspecting your actual stack, build commands and conventions, then traces a single user journey: interface state change, API request, authorization, data access, response handling.
The workflow splits work into stages: define the request/response contract, permission checks, input validation and failure modes; implement the smallest coherent slice using existing dependencies; run the project's own checks—unit tests for rules, integration tests for permissions and persistence, browser tests for the complete journey. Then prepare migration, rollback and release plans.
Example: add a billing settings page. Inspect the existing billing integration and account permissions, define the settings API, implement loading/empty/error states, test that one account cannot modify another's settings. Keep provider writes and migrations separate from local implementation; do not spin up a paid subscription just to test the UI.
What it helps with
- verify feature coherence from UI through database to response
- define API contracts and access permissions before coding
- separate domain logic, persistence and presentation correctly
- prepare migration and rollback plans for production
- run checks for changed behavior across layers
Example prompts for the agent
- Add a billing settings page where users can change payment method
- Implement full-stack: from UI filter through API request to result caching
- Review the notification system end-to-end: how does a request flow from client through database to email
How to install senior-fullstack
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill senior-fullstack -a claude-code2Manually: put the files in place
~/.claude/skills/senior-fullstack/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/senior-fullstack/
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill senior-fullstack -a codex2Manually: put the files in place
.agents/skills/senior-fullstack/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill senior-fullstack -a cursor2Manually: put the files in place
.cursor/skills/senior-fullstack/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install sickn33/agentic-awesome-skills senior-fullstack2Manually: put the files in place
.github/skills/senior-fullstack/SKILL.md1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill senior-fullstack -a gemini-cli2Platform CLI
gemini skills install https://github.com/sickn33/agentic-awesome-skills --path skills/senior-fullstackManually: put the files in place
.devin/skills/senior-fullstack/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill senior-fullstack -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set80
The whole set →Other versions of senior-fullstack
Similar
Questions about senior-fullstack
How do I install senior-fullstack in Claude Code?
Run npx skills add sickn33/agentic-awesome-skills --skill senior-fullstack -a claude-code, then find the skill at ~/.claude/skills/senior-fullstack/SKILL.md.
What does senior-fullstack do?
It guides implementation of features crossing layer boundaries: UI, backend, database. It verifies API contracts, access permissions, input validation and migrations; runs unit, integration and browser tests.
What are the limitations?
Stack and provider compatibility must be verified in your actual project. The references are review checklists, not application templates. Passing tests does not guarantee security or deployment readiness.
Source text
SKILL.md · MIT
--- name: senior-fullstack description: "Coordinate full-stack implementation across interface, service, database and delivery boundaries using the existing project stack and verified checks." risk: critical source: community date_added: "2026-02-27" --- # Full-Stack Implementation Review ## When to Use Use when a feature spans the browser, backend service and database, or when reviewing an existing full-stack implementation for integration gaps. ## Workflow 1. Inspect the project's actual stack, build commands and conventions. Trace one user journey through interface state, API request, authorization, data access and response handling. 2. Define the request/response contract, permission checks, input validation and failure states before changing code. Keep database migrations and external side effects explicit. 3. Implement the smallest coherent slice using existing dependencies. Separate interface presentation, domain logic and persistence; use parameterized queries and server-side authorization. 4. Run project-owned checks for the changed behavior: unit tests for rules, integration tests for permissions and persistence, and browser tests for the complete journey. Record which checks actually ran and any missing environments. 5. Prepare a migration, rollback and release plan where needed. Dependency installation, destructive data changes, external notifications and deployments require authorization appropriate to that action. ## Example User: "Add a billing settings page." Assistant: Inspect the existing billing integration and account permissions, define the settings API, implement loading/empty/error states, and test that one account cannot modify another account's settings. Prepare provider writes and deployment separately from local implementation; do not create a paid subscription merely to test the interface. ## Bundled references - [Stack inspection checklist](references/tech_stack_guide.md) - [Boundary and contract review](references/architecture_patterns.md) - [Implementation and verification workflow](references/development_workflows.md) ## Helper status The three retained Python helpers are unimplemented historical skeletons. They intentionally fail with a nonzero exit and do not scaffold, analyze quality or certify a project. Use the project's real tools; do not report an empty findings list as a clean audit. No executable installation or production deployment is supplied by this skill. ## Limitations - Stack and provider compatibility must be checked in the actual project. - The references are review checklists, not complete application templates. - Passing a subset of tests does not prove security, performance or deployment readiness. - Do not infer permission to change accounts, billing or production resources from a request for a code review.
© sickn33 · MIT · sickn33/agentic-awesome-skills