Full-stack development: backend architecture, API design and frontend integration
Mandatory workflow for building full-stack apps — requirements, decisions, scaffold checklists, patterns for config, errors, DB, auth, caching, real-time and production hardening
- What
- Mandatory workflow for building full-stack apps — requirements, decisions, scaffold checklists, patterns for config, errors, DB, auth, caching, real-time and production hardening
- Cost
- Free
- Needs
- a full-stack project to build (the skill is a methodology the agent follows, not software to install)
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @minimax-ai's full-stack development playbook: a mandatory 5-step workflow the agent must follow before writing any code — gather requirements (stack, service type, database, integration, real-time, auth), state architectural decisions (feature-first vs layer-first, API client approach, auth strategy, real-time method), scaffold from two checklists (backend service: typed config with fail-fast env validation, typed error hierarchy, structured logging, migrations, input validation, health checks, graceful shutdown, CORS with explicit origins; frontend-backend integration: typed API client, base URL from env, token interceptors, loading states, shared types), then implement, test and hand off. Thirteen pattern sections cover project structure (controller → service → repository, feature-first layout), configuration, error handling, database access (N+1 prevention, transactions, pooling), API clients (typed fetch, React Query, tRPC, OpenAPI codegen), JWT auth with transparent refresh and RBAC, logging, idempotent background jobs, caching, presigned-URL file uploads, real-time (polling vs SSE vs WebSocket decision table), cross-boundary error mapping, and production hardening — plus deep-dive references for testing strategy, release checklist, technology selection, Django, API design, DB schema and auth flows, with TypeScript, Python and Go examples. MIT licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a full-stack project to build (the skill is a methodology the agent follows, not software to install) Install "Full-stack development: backend architecture, API design and frontend integration" for me. It gives my agent @minimax-ai's full-stack playbook: a mandatory 5-step workflow (gather requirements, state architectural decisions, scaffold from backend-service and frontend-integration checklists, implement following the patterns, test and hand off), covering feature-first project structure, typed fail-fast config, typed error hierarchies, database patterns (migrations, N+1 prevention, transactions, pooling), API client options (typed fetch, React Query, tRPC, OpenAPI codegen), JWT auth with refresh and RBAC, structured logging, idempotent background jobs, caching, file uploads, real-time (polling/SSE/WebSocket), and production hardening. MIT-licensed. Repository: https://github.com/minimax-ai/skills/blob/main/skills/fullstack-dev/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). Review the files for suspicious commands or credential handling; stop on any red flag and never assume the repository is safe. Tell me if anything looks off. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "fullstack-dev". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. tell the agent the stack and requirements for the app to build; nothing else — it's a methodology). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.