Project-scoped structural context: codebase onboarding, code maps, documentation upkeep, conventions, domain modeling, and CLAUDE.md scaffolding. Structural context only; it stores no history (B-4).
Plugin domain from marketplace awakened in coltonbearden/awakened. Commands read from the repo's manifest — 1 month ago.
ai-readable-docsWrite, convert, or validate technical documentation in a dual-audience Markdown convention (HADS) where every block is tagged as verified fact, human context, confirmed failure with fix, or unverified claim, and a reading manifest at the top tells a model what to read and skip. Use when documentatio
codebase-designShared vocabulary and method for designing deep modules — much behaviour behind a small interface, placed at a real seam, tested through that interface. Use when designing or reshaping a module's interface, deciding where a seam belongs, finding shallow pass-through code worth merging, making code e
codebase-onboardingSurvey an unfamiliar repository and produce an onboarding guide — stack, architecture shape, entry points, one traced request path, conventions, common commands — plus a starter or refreshed project CLAUDE.md. Use on first contact with a repository, when the user asks to be walked through a codebase
crafting-readmesWrite, extend, refresh, or review a README so it answers the questions its actual readers will bring, with a section set matched to the project type instead of one generic template. Use when a project has no README, a capability changed and the README went stale, a new section is needed, or the user
domain-modelingBuild and sharpen a project's domain glossary while design is happening — challenge vague or conflicting terms, probe relationships with concrete scenarios, check claims against the code, and record each resolved term in CONTEXT.md as it crystallises. Use when the conversation is defining or renamin
inherit-legacy-styleExtract the implicit conventions of a hand-written codebase into an enforceable rules file so generated code follows the project's own idioms instead of mainstream defaults. Use when onboarding an AI agent onto a legacy project, when generated code keeps drifting from house style, or when the user w
living-docs-governanceAssign a long-lived project's existing documents four non-overlapping roles — constitution, map, status, history — link them from the project CLAUDE.md, and set the update rules that keep each fact with one owner. Use when docs drift from code, when the same structure is rediscovered every session,
/domain:update-codemapsGenerate or refresh token-lean architecture codemaps under docs/CODEMAPS/ — layout, entry points, request paths, data shape, and external dependencies — each capped near 1000 tokens with a freshness line. Use after a large feature lands, after a refactor, or when Claude keeps re-deriving the same st
/domain:update-docsRegenerate the generated sections of project documentation from declared sources of truth — build scripts, environment templates, route definitions or API specs, public exports, and container files — then flag docs that look stale. Use when scripts, variables, or endpoints changed and the docs did n
Specialist subagents with restricted tool allowlists: research, exploration, debugging, review, planning, documentation, and synthesis agents, plus the skills that dispatch them. Every subagent in Awakened lives here (B-6).
7 skills · 27 agents
Core engineering workflow: planning, implementation discipline, test-driven development, systematic debugging, verification before completion, and git workflow guidance. The stable baseline - it depends on no agents, memory infrastructure, or project-specific tooling (B-1).
18 skills · 9 commands
Marketplace meta tooling: skill creation, writing for agents, context budgeting, skill scouting, component auditing, and linting. Marketplace maintenance, not user workflow execution (B-7).
6 skills · 2 commands
Code review and analysis: review discipline, production audit, architecture inspection, AI-debt detection, and security-oriented review. Analysis and review only - implementation stays outside this plugin (B-2).
7 skills · 1 command
Session management and momentum: save and resume sessions, handoffs, checkpoints, and focused asides. Session momentum only - it duplicates no planning, debugging, or review system (B-5).
1 skill · 4 commands
Persistent temporal memory: file-based decision history, session context, searchable project notes, and recall across sessions. No daemons, workers, databases, or services (B-3).
3 skills · 2 commands
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
15 skills · hooks
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
Perform AI code review on Git diffs — supports workspace changes, branch ranges, and single commits with concurrent per-file analysis, codebase search, and deep context-aware review.
2 commands
Context-Driven Development plugin that transforms Claude Code into a project management tool with structured workflow: Context → Spec & Plan → Implement
3 skills · 6 commands · 1 agent
Long-term semantic memory for Claude Code, powered by OpenViking
5 skills · 1 command · 1 MCP server · hooks
Search and retrieve documents from local markdown files.
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.