Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Drive a spec-first development workflow in TypeScript monorepos: specify features, generate plans with numbered slices, execute slices with verification, create changesets, and get code reviews — all with conventions for changelogs, JSDoc, markdown, and writing style.
npx claudepluginhub stijnvanhulle/template --plugin toolkitCreate a Changeset for the current changes with the right semver bump
Work a feature's slices one at a time, ticking each slice's Done criteria as it passes
Turn a feature's spec and research into its plan.md (architecture + numbered slices) and scaffold the slice files
Draft or refine the Phase 0 spec (requirements + acceptance criteria) for a feature
Fill a feature's verification.md with scenarios mapped to acceptance criteria, then run them
Creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes.
Always-on conventions for TypeScript monorepos. Use when writing or reviewing TypeScript, markdown, or tests, when handling secrets, env vars, or input at trust boundaries, or any time you would otherwise reach for a project style guide. Bundles code style, JSDoc, markdown structure, security, and testing rules.
Use when writing blog posts or documentation markdown files - provides writing style guide (active voice, present tense), content structure patterns, and SEO optimization. Overrides brevity rules for proper grammar.
Remove AI writing patterns to make documentation sound natural, specific, and human. Covers content patterns, language patterns, style patterns, and communication patterns.
Full JSDoc format guide for TypeScript, covering @example formats (short, multi-line, multi-variant), tag usage (@default, @deprecated, what to avoid), documentation patterns for properties/enums/functions, and tag order.
Structured planning mode that researches and produces an implementation plan, with no code edits
Concise, direct replies and clean prose in the repo's house voice, while keeping normal coding behavior
Lead structural explanations with a Mermaid diagram, then prose
Runs pre-commands
Contains inline bash commands via ! syntax
Bash prerequisite issue
Uses bash pre-commands but Bash not in allowed tools
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Autonomous spec-driven development workflow with multi-agent collaboration, specification management, and task orchestration
Spec-driven development plugin for Claude Code. Markdown specs as the source of truth, code downstream.
Comprehensive AI-assisted development workflow system with specialized agents, orchestrated commands, and file-based state management
Spec-driven development using GitHub spec-kit methodology. Constitution-first approach with specify, plan, tasks, and implement phases.
GitHub Spec-Kit integration for Specification-Driven Development - define WHAT and HOW before coding
Skills-first specification-driven development framework with 7 agent skills for planning, implementation, review, and shipping. Natural language activation with intelligent agent orchestration. Includes /plan, /implement, /research commands plus managing-specifications, implementing-features, and reviewing-and-shipping skills.
[![Stars][stars-src]][stars-href] [![License][license-src]][license-href] [![Coverage][coverage-src]][coverage-href]
A modern TypeScript monorepo template (pnpm workspaces, Turborepo, oxlint, oxfmt, tsdown, Vitest, and Changesets).
A drop-in monorepo starter. Fork it, rename a few fields, and you have a production-ready repository with build, test, lint, format, release and CI already wired up.
This template is set up for AI coding agents. It builds on two open formats, AGENTS.md and Agent Skills, and uses symlinks so every tool reads from one source instead of drifting copies.
AGENTS.md is the canonical instruction file. The shared toolset (skills, commands,
code-reviewer agent, output styles, and conventions) lives in tools/claude/, which doubles as
a Claude Code plugin (installable as toolkit@stijnvanhulle). The workspace paths under .claude/ and .agents/
symlink into that folder, so the template repo and any project that installs the plugin run
the same content from a single source of truth. See tools/claude/README.md
for install steps.
AGENTS.md # canonical instructions every agent reads
CLAUDE.md → AGENTS.md # Claude Code
GEMINI.md → AGENTS.md # Gemini CLI
.github/copilot-instructions.md → AGENTS.md # GitHub Copilot in VS Code
tools/claude/ # distributable Claude Code plugin (single source of truth)
├── .claude-plugin/plugin.json # plugin manifest
├── README.md # install + usage
├── skills/ # cross-provider Agent Skills, one SKILL.md folder each
│ ├── changelog, documentation, humanizer, jsdoc, pr, spec-driven
│ └── conventions/ # always-on rules: code-style, jsdoc, markdown, security, testing
├── commands/ # slash commands: /changeset, /spec, /plan, /implement, /verify
├── agents/ # subagents: code-reviewer
└── output-styles/ # system-prompt modes: house (default), plan, diagrams-first
.agents/
└── skills → ../tools/claude/skills # lets cross-provider runtimes find the shared skills
.claude/ # Claude-specific workspace config
├── settings.json # permissions and hook registration
├── hooks/ # shell hooks: session-start, format-lint, guard-edit
├── skills → ../tools/claude/skills # all seven skills, including conventions
├── commands → ../tools/claude/commands
├── agents → ../tools/claude/agents
├── output-styles → ../tools/claude/output-styles
└── rules → ../tools/claude/skills/conventions # the conventions skill files, exposed as rules
plans/ # spec-driven workflow
├── README.md # workflow guide
├── templates/ # blank docs, copied per feature
│ ├── spec.md # requirements and acceptance criteria
│ ├── research.md # decisions, open questions, constraints
│ ├── plan.md # architecture and numbered slices
│ ├── verification.md # end-to-end scenarios, one per AC
│ └── slice.md # one implementation slice
└── <feature>/ # one folder per plan
├── spec.md research.md plan.md verification.md
└── NNN-<slug>.md # slices, copied from templates/slice.md
Supported agents:
CLAUDE.md (symlink to AGENTS.md) and .claude/skills (symlink to
tools/claude/skills), plus the Claude-specific extensions below. Other projects can install
the same toolset as a marketplace plugin (see tools/claude/README.md).AGENTS.md and Agent Skills natively.AGENTS.md natively, and .github/copilot-instructions.md
(symlink to AGENTS.md) in VS Code.AGENTS.md natively. It does not follow symlinks into .cursor/rules/,
so rules are not duplicated there. The rule files under .claude/rules/ are referenced from
AGENTS.md instead.AGENTS.md and Agent Skills natively.GEMINI.md (symlink to AGENTS.md).AGENTS.md natively.