Default web stack expertise for the AIDLC pipeline: TypeScript standards + strict tooling baseline (ESLint/Prettier/tsconfig/.gitattributes + optional husky/lint-staged) + enterprise project structure (scaffold + dependency-cruiser boundary gate) + the Node/TS CI half (templates, the npm gate, isolated-checkout dependency resolution, cross-platform lockfiles) + the Prettier auto-format hook, Next.js, NestJS, Postgres, MongoDB, DB migrations, Docker, API design.
Plugin aidlc-stack-web from marketplace aidlc in Sourabh1095/AIDLC. Commands read from the repo's manifest — 13 days ago.
This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.
api-designREST contract conventions between the Next.js frontend and NestJS backend — naming, status codes, error shape, pagination, versioning, OpenAPI. Load when adding or changing API endpoints.
ci-webThe Node/TypeScript half of CI — shipped templates, the typecheck/lint/format/boundaries gate, cross-repo resolution, lockfiles, reproducing a red run locally. Load together with aidlc:ci-cd on a Node/TS repo.
coding-standards-tsTypeScript coding standards — typing, error handling, naming, module structure, async. Load when writing or reviewing TypeScript or JavaScript on the web stack.
db-migrationsMigration safety — expand-contract, rollback, backfills and risky-DDL rules for Postgres and MongoDB. Load whenever a change touches schema or indexes, or needs a backfill.
dockerDocker conventions — multi-stage Node builds, compose dev environments, image hygiene, container security, running the CI image locally. Load for Dockerfiles or compose files, build or run changes, or a CI failure that won't reproduce locally.
mongodbMongoDB conventions — document modeling, indexes, aggregations and update discipline. Load when designing collections, writing queries or reviewing MongoDB changes.
nestjsNestJS conventions — module boundaries, dependency injection, DTO validation, errors, configuration, testing. Load when implementing, planning or reviewing NestJS backend work.
nextjsNext.js App Router conventions — server/client split, data fetching, server actions, routing, caching, performance. Load when implementing, planning or reviewing Next.js frontend work.
postgresPostgreSQL conventions — schema design, indexing, query patterns and review heuristics. Load when designing schemas, writing queries or reviewing Postgres changes.
project-structureEnterprise project structure for the web stack — folder trees, layering rules and state/data conventions for NestJS and Next.js or SPA frontends. Load when scaffolding a repo, placing new code, or reviewing that code sits in the right layer.
node "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/format.mjs"
AIDLC (AI Development Life Cycle) orchestrator: reads work items (Jira/ADO/markdown), routes them through requirements, planning, implementation, review, QA and PR — across one repo or a multi-repo workspace, with or without a git remote, end to end. Stack-agnostic by design; language and framework expertise comes from stack packs.
52 skills · 9 agents · 1 MCP server · hooks
UI/UX pod that starts from whatever already exists. Screens in Figma → it ships the Figma MCP, extracts the spec and variables, builds to the design and gates on fidelity, with the jury offered rather than imposed. A brand design system in Figma → its variables and components become the project's tokens and vocabulary (workspace-wide), and the pod designs the screens within them, jury still gating. Neither → UX-narrative writer, Awwwards inspiration researcher, design-system owner, motion specialist, and a strict unbiased jury that renders the UI and gates on ≥9/10. New or existing projects, page or whole-app scope, honors brand references (logo/colors/fonts). Bundles the Figma and Playwright MCP servers it needs, so a backend-only workspace installs neither. Enabled by default; it only activates on UI items, so backend-only projects are unaffected.
8 skills · 7 agents · 2 MCP servers
The Azure DevOps MCP server for AIDLC's ADO adapter. Optional — the adapter's `az boards`/`az rest` tier covers every operation and is what headless runs already use, so ADO works without this. Install it for the richer interactive tier; needs ADO_MCP_ORG in the launching shell.
1 MCP server
The Atlassian MCP server for AIDLC's Jira adapter. Required when workItems.source is "jira" — that adapter has no CLI fallback. Install only on Jira projects; core ships no tracker server, so a markdown or ADO workspace starts neither.
1 MCP server
A mod (Claude Code 2.1.287+) that shows AIDLC beside the chat: a line above the prompt with the runs in flight and anything waiting on you, a board pane for runs and the sprint, /aidlc-board with no model turn, a desktop notification when a sprint run needs you, the module you're changing and what uses it, this session's files and checks, each epic as a tree of its stories, tasks and bugs, and what each work item cost by phase (feeds /aidlc:insights). It draws what core's scripts report, calls no model and gates nothing; it writes only its git-ignored cost ledger and board copy. Optional: AIDLC works the same without it, which matters where an organization allows only its own mods.
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
15 skills · hooks
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
6 skills
Up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your coding agent's context.
1 MCP server
Build powerful, stateful CLI interfaces for any GUI application using the cli-anything harness methodology.
5 commands
Automates browser interactions for web testing, form filling, screenshots, and data extraction
12 skills
Use Alibaba Open Code Review from local Codex.
2 skills
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.