master-developer
/master-developer
Senior full-stack engineering workflow for Next.js, Node/Express, TypeScript, Prisma/PostgreSQL, Redis and Three.js work. Use when building or changing apps, APIs, bots, portfolios or 3D pages; fixing bugs; reviewing security (OWASP Top 10:2025); hardening, testing or deploying. Loads topic rules on demand.
- Author
- Badhon-00 ↗
- Repository
- MDCP ↗
- Licence
- MIT
- Last repository change
- 11.11.2026
Assessment and security
- Files in this package
- 37
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 11.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Senior full-stack engineering workflow for Next.js, Node/Express, TypeScript, Prisma/PostgreSQL, Redis and Three.js work. Use when building or changing apps, APIs, bots, portfolios or 3D pages; fixing bugs; reviewing security (OWASP Top 10:2025); hardening, testing or deploying. Loads topic rules on demand.
Original author description
Senior full-stack engineering workflow for Next.js, Node/Express, TypeScript, Prisma/PostgreSQL, Redis and Three.js work. Use when building or changing apps, APIs, bots, portfolios or 3D pages; fixing bugs; reviewing security (OWASP Top 10:2025); hardening, testing or deploying. Loads topic rules on demand.
How it works
- Core rules
- Which reference to open
- Companion skills in this plugin
- Limits
SKILL.md preview
--- name: master-developer description: Senior full-stack engineering workflow for Next.js, Node/Express, TypeScript, Prisma/PostgreSQL, Redis and Three.js work. Use when building or changing apps, APIs, bots, portfolios or 3D pages; fixing bugs; reviewing security (OWASP Top 10:2025); hardening, testing or deploying. Loads topic rules on demand. --- # Master Developer Working rules for production-quality code. Open only the reference files the task needs. ## Core rules 1. Read the code you will touch and its callers first. Follow the project's existing structure; add no files or features nobody asked for. 2. Do not break working code. New feature = new module; edit old files only when needed, with a small diff. 3. Start. Pick sensible defaults and say which. Ask one short question only when a wrong guess is costly or irreversible (data deletion, production deploy, paid services, public publishing). 4. Verify by running: `npx tsc --noEmit`, lint, tests, `npm run build`. Report results as they are, and name what was not run. 5. Security is part of every feature: validate input (Zod), authorize every route and object, parameterized queries, secure headers, no secrets in code, rate limits on public and auth routes. 6. Bug fixes: reproduce, find the root cause, fix it once in shared code, add a regression test. After three failed attempts, stop and report. 7. Never claim "100% secure" or "bug-free". Report evidence. 8. Output: new files whole, edits as diffs. End with what changed, what was not checked, and any risk. ## Which reference to open | Task | File in `references/` | |---|---| | Starting any task, working style | senior-developer.md, project-rules.md, supreme-executor.md | | Context and token use, long sessions | llm.md, token.save.md, token-compressor.md, infinite-runtime.md | | UI, design tokens, layout | uiux.md, design-tokens.md, frontend-architecture.md | | 3D, animation | threejs.md, performance.md | | APIs and backend | api.md, backend.md | | Database, Prisma, Supabase RLS | database.md | | Encryption, hashing, JWT, key handling | security.md, crypto-vault.md | | Security review (OWASP 2025) | security-check.md, web-analysis-shield.md | | Scanning and self-testing own app | vulnerability.md, exploit-sandbox.md | | Tests and quality gates | testing.md, zero-error-validator.md, absolute-perfection.md | | Errors and bug loops | bugfix-loop.md, self-heal-engine.md | | Release | deployment.md, auto-git-manager.md | | Tools and MCP servers | mcp.md, mcp.json, auto-installer.md | | New site, app or bot from a short request | omni-creator.md | | Overview | master-manifest.md, singularity-core.md, CLAUDE.md | | Reverse engineering (authorized targets only) | reverse-engineering.md | ## Companion skills in this plugin Use these when the task matches; they are bundled unmodified (see THIRD_PARTY_NOTICES.md). - Security and quality: security-review, security-scan, agent-security-hardening, mcp-dependency-review, tdd-workflow, verification-loop, coding-standards, e2e-testing, webapp-testing - Backend and data: api-design, backend-patterns, database-migrations, postgres-patterns, prisma-patterns, docker-patterns, deployment-patterns, mcp-builder - Frontend and UI/UX: frontend-patterns, frontend-a11y, nextjs-turbopack, web-design-guidelines (UI review), react-best-practices, composition-patterns, react-view-transitions - Design (Anthropic): frontend-design, canvas-design, algorithmic-art, brand-guidelines, theme-factory, web-artifacts-builder; ui-ux-pro-max (searchable palettes, fonts, styles, UX rules: `python3 scripts/search.py "<product> <style>" --design-system`) - Building skills and Claude API apps: skill-creator, claude-api - Workflow (planning, debugging, review, branches): writing-plans, executing-plans, systematic-debugging, test-driven-development, verification-before-completion, requesting-code-review, receiving-code-review, finishing-a-development-branch, dispatching-parallel-agents, using-git-worktrees, subagent-driven-development - Building plugins, hooks, agents, MCP servers: plugin-structure, plugin-settings, skill-development, command-development, agent-development, hook-development, mcp-integration, build-mcp-server, build-mcpb, build-mcp-app; CLAUDE.md upkeep: claude-md-improver - 3D (Three.js): threejs-fundamentals, threejs-geometry, threejs-materials, threejs-lighting, threejs-textures, threejs-animation, threejs-interaction, threejs-loaders, threejs-shaders, threejs-postprocessing, threejs-performance, threejs-asset-pipeline, threejs-react-three-fiber - MDCP own: mdcp-self-check (self-check, defense review, self-debug), mdcp-token-meter (session usage readout) - Cloning an app's features, clean-room (public sources only, rebrand before launch): replica-recon, replica-architect, replica-design, replica-build, replica-backend, replica-test, replica-diff, replica-entrepreneur, replica-brand, replica-launch, replica-deploy ## Limits These rules guide behavior; CI (build, typecheck, tests, scanners) enforces it.
Files in this package (37)
- SKILL.md 5 KB
- references/CLAUDE.md 3 KB
- references/absolute-perfection.md 1 KB
- references/api.md 1 KB
- references/auto-git-manager.md 1 KB
- references/auto-installer.md 1 KB
- references/backend.md 1 KB
- references/bugfix-loop.md 1 KB
- references/crypto-vault.md 1 KB
- references/database.md 1 KB
- references/deployment.md 1 KB
- references/design-tokens.md 1 KB
- references/exploit-sandbox.md 1 KB
- references/frontend-architecture.md 1 KB
- references/infinite-runtime.md 1 KB
- references/llm.md 1 KB
- references/master-manifest.md 1 KB
- references/mcp.json 1 KB
- references/mcp.md 1 KB
- references/omni-creator.md 1 KB
- references/performance.md 1 KB
- references/project-rules.md 1 KB
- references/reverse-engineering.md 1 KB
- references/security-check.md 1 KB
- references/security.md 1 KB
- references/self-heal-engine.md 1 KB
- references/senior-developer.md 1 KB
- references/singularity-core.md 1 KB
- references/supreme-executor.md 1 KB
- references/testing.md 1 KB
- references/threejs.md 1 KB
- references/token-compressor.md 1 KB
- references/token.save.md 1 KB
- references/uiux.md 1 KB
- references/vulnerability.md 1 KB
- references/web-analysis-shield.md 1 KB
- references/zero-error-validator.md 1 KB
Versions
The database has no other skills named master-developer.
Database snapshot: 13.11.2026 · package version f11acd075ae1 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90node-api-rules
Shipwright rules and check commands for Node API (Fastify or Express, Prisma, PostgreSQL, Redis, Socket.io). Use when writing, reviewing or auditing code in a project that uses this stack. FR : règles et commandes de vérification pour API Node (Fastify ou Express, Prisma,… - 100typescript-full-stack
Use when building end-to-end TypeScript applications — Node backend (Fastify), React/Next frontend, shared types via tRPC or Zod, monorepo with turborepo/nx, Prisma/Drizzle data layer, end-to-end type safety. - 90node-typescript-backend
Build production Node.js/TypeScript backends (Fastify, NestJS, Express): structure, validation, async, errors, config, testing, performance. Use when writing or reviewing Node/TS services or APIs. - 100express
Express.js backend stack patterns for routing, middleware, error handling, TypeScript setup, and testing. Use when building or refactoring a Node.js Express service. - 100prisma-postgres-upgrade
Upgrade a PostgreSQL app from Prisma ORM 6 or 7 straight to Prisma 8 in one pass, keeping the existing schema.prisma, database and data. Use when a Postgres project on Prisma 6 or 7 wants Prisma 8, including before deploying it on Prisma Compute, which runs only Prisma 8.… - 100javascript-typescript
Professional JavaScript and TypeScript development skill covering modern ES6+, TypeScript, Node.js, Express, React, testing frameworks, and best practices. Use this skill when developing JavaScript/TypeScript applications, building React/Node.js projects, implementing RESTful…