Menu
Linting workflows with neostandard and ESLint v9 flat config
Personalize a freshly cloned `metaimed-starter` (or compatible type-cascade monorepo) by interviewing the user about project name, primary domain, audience, tone and brand, then rendering AGENT.md, CLAUDE.md, and design/*.md from the answers, generating ENCRYPTION_KEY + JWT_SECRET_KEY, installing dependencies, bringing up docker-compose, applying the initial Prisma migration + triggers, and finally spawning checkpoint agents in sequence (design system → auth vertical → first CRUD domain → deploy infra) with user review between each. Use when the user opens a fresh clone of this starter and asks to "initialize the project", "personalize the starter", "set up the new project", "let's begin", "start building" or any first-day greenfield request. Skip cloning — assume the working directory is already a starter clone.
Technical writer specializing in the Diátaxis documentation framework
Comprehensive best practices for Fastify development
Best practices for Node.js development with TypeScript using type stripping
Deep Node.js internals expertise including C++ addons, V8, libuv, and build systems
OAuth 2.0/2.1 specification expert with deep RFC knowledge and Fastify integration patterns
| name | linting-neostandard-eslint9 |
| description | Linting workflows with neostandard and ESLint v9 flat config |
| metadata | {"tags":"linting, neostandard, eslint, eslint9, flat-config, javascript, typescript"} |
Use this skill when you need to:
neostandard as a Standard-like ESLint v9 flat-config baselineeslint@9 with the flat config system (eslint.config.js/eslint.config.mjs)standard to neostandard or ESLint v9.eslintrc* configuration to ESLint v9Read individual rule files for implementation details and examples:
standard to neostandard or ESLint v9.eslintrc* to flat config safely