Agent skill · software engineering · sickn33
senior-fullstack
Coordinate full-stack implementation across interface, service, database and delivery boundaries using the existing project stack and verified checks.
Why this skill is useful
Adds 3 executable scripts for fullstack development that automate scaffolding, analysis, and code quality checks, which are not commonly found in public resources.
What it needs
Requires docker, npm, python installed locally. About 1k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
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 Boundary and contract review Implementation and verification workflow 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/senior-fullstack--941f20