Shared infrastructure and patterns for spec-kit specification-driven development. Triggers: spec-kit patterns, tech-stack patterns, checklist dimensions, artifact structure, specification infrastructure, shared templates Use when: developing new spec-kit skills, referencing standard patterns, ensuring consistency across specification workflows DO NOT use directly: this skill is infrastructure for other spec-kit skills. Provides reusable patterns consumed by all spec-kit commands and skills.
/plugin marketplace add athola/claude-night-market/plugin install sanctum@claude-night-marketThis skill inherits all available tools. When active, it can use any tool Claude has access to.
modules/artifact-structure.mdmodules/checklist-dimensions.mdmodules/tech-stack-patterns.mdProvides common patterns, templates, and infrastructure modules used across all spec-kit commands and skills. This skill exists to reduce duplication and maintain consistency in specification-driven development workflows.
This skill consolidates reusable components:
Technology-specific patterns for common stacks and tools:
Quality validation dimensions for requirement testing:
Spec-kit artifact organization and purpose:
This skill is automatically loaded by speckit-orchestrator and referenced by other spec-kit skills. It should not be loaded directly by commands.
speckit-orchestrator: Workflow coordinationspec-writing: Specification creationtask-planning: Task generationThis skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.