Repository navigation
Attributions
This page lists the outside works that dotclaude 1.0.0 uses.
Read it if you check the license of a work that dotclaude uses.
Each row gives the license that the source states.
Where the source states no license, the row says not stated.
| Work | Link | License | What dotclaude 1.0.0 uses it for |
|---|---|---|---|
| agent-skills by Addy Osmani | addyosmani/agent-skills | MIT | An idea. The description of each skill and agent states what it does and when to use it. If a neighbor skill can match the same request, the description adds a Not for part. |
Context7 with the ctx7 CLI |
context7.com, upstash/context7 | MIT for upstash/context7. Not checked for the ctx7 package. |
The docs skill of dotclaude-docs runs ctx7 with bunx to read the current docs of a library. |
| agent-browser | vercel-labs/agent-browser | Apache-2.0 | The default backend of dotclaude-browser. The browse skill and the WebSearch answer run it. |
| CloakBrowser | CloakHQ/cloakbrowser | MIT for the wrapper code. The compiled binary has its own terms. | The optional cloakbrowser backend. agent-browser runs the CloakBrowser binary through --executable-path. |
CodeGraph CLI codegraph from @colbymchenry/codegraph
|
colbymchenry/codegraph | MIT | The dotclaude-codegraph plugin runs codegraph to sync the index and to read the code graph. |
jev CLI by pedramamini |
gist | MIT, as the gist README states | An idea. The verbs are short: yes, pick, and ask. Keys replace list positions. The dotclaude-decide command of the core plugin has these verbs. The TypeSafe API gives the answers. The gist also has a rating verb, which 1.0.0 does not use. |
These works are the research for the redesign of the spec store of 1.0.0. dotclaude cites them and copies no text from them. The last column says what dotclaude uses from each work. Spec Store Choices gives the choices and the alternatives that dotclaude did not take.
| Work | Link | License | What dotclaude uses |
|---|---|---|---|
| Bruno Claudino, Ruizhe Xing, Yuanhao Zuo, Tyler Menezes, Anita Sarma, Kostadin Damevski, and Zixuan Feng, "The EPIC Framework for Spec-Driven Development", 2026 | arXiv:2610.07534 | CC BY 4.0 | Gates that the CLI checks before a state change, and the marker [NEEDS CLARIFICATION: ...] that blocks implement. |
| Deepak Babu Piskala, "Spec-Driven Development: From Code to Contract in the Age of AI Coding Assistants", 2026 | arXiv:2602.00180 | CC BY 4.0 | The phases specify, plan, and implement, and the --decision fix-code or --decision revise-spec after a failed verify. |
| Subham Panda, "Citation Discipline in Spec-Driven Development: A Cross-Model Empirical Study of Output Determinism and Automated Hallucination Detection in LLM-Generated Code", 2026 | arXiv:2606.30689 | CC BY 4.0 | Stable REQ-<n> IDs and satisfies. dotclaude does not take the per-line citations of traceSDD, and the reason is on Spec Store Choices. |
| Vu Hung Nguyen and Thanh Nguyen, "SDAD: Spec-Driven Agentic Development for the AI-Native SDLC", 2026 | arXiv:2608.20341 | CC BY-SA 4.0 | Human merge authority, with the SHA of the approval in approve and merge, and the event log of each step. |
| Jessica Diaz, Joaquin Gayoso, Andrea Cimminio, and Jorge Perez, "Spec-Driven Development for Agentic Software Engineering: Harnessing Human-Agent Teamwork", 2026 | arXiv:2609.00252 | arXiv non-exclusive distribution license 1.0 | The evidence in each event, such as the command, the exit status, and the SHA. |
| Srinivas Rao Marri, "Constitutional Spec-Driven Development: Enforcing Security by Construction in AI-Assisted Code Generation", 2026 | arXiv:2602.02584 | CC BY 4.0 | A brief that holds only the requirements of its package. |
| Jimmy Song, "YAML to Markdown: Exploring Specification Driven Development and AI-Native Paradigms", 2025 | jimmysong.io | CC BY 4.0, as the page footer states | Markdown with front matter as the format of the store. |
The CloakBrowser binary has its own terms.
From v148, the binary needs an active CloakBrowser Pro subscription to download.
Earlier builds are free, with restrictions on redistribution.
Read the BINARY-LICENSE.md file of that project for the full terms.
dotclaude ships no npm package.
The packages in the root package.json are dev tools for the repository.
These are @biomejs/biome, @types/node, bun-types, markdownlint-cli2, and yaml.
The shipped code in plugins/ imports only the node: built-in modules and the claude-code plugin types.
- Home: the overview.
- Architecture: the core plugin.
-
Second Opinion: the
dotclaude-decidecommand. - Skills: the skill descriptions.
- Browser, Code Graph, and Library Docs: the add-on plugins that call the CLIs.
- Start
- How dotclaude Works
- Add-On Plugins
- How Claude Code Works
- Reference
- Rationale
- Evidence
- Development
- Archive