Framework
Owns the installation record and everything done to a project, under src/contexts/framework/ — the manifest aggregate, and the setup/install/restore/uninstall/doctor orchestration built on top of it. This is the only context allowed to reach `translate` and `distribution`. Use when adding a use-case that touches the manifest, a setup/doctor/sync/uninstall flow, a new top-level CLI orchestration, or a launcher that runs an external binary (kanban-shaped). Do NOT use for a tool's own profile or capability classes — use `tools`. Do NOT use for the translation pipeline — use `translate`. Do NOT us
Install
/plugin marketplace add ai-driven-dev/frameworkThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add ai-driven-dev/framework --skill frameworkgit clone --depth 1 https://github.com/ai-driven-dev/framework.git /tmp/framework
mkdir -p ~/.claude/skills
cp -r /tmp/framework/cli/.claude/skills/framework ~/.claude/skills/frameworkPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Framework `framework` is what is posed on a project and the record of it: the manifest that tracks every installed file, and every flow that reads or changes that record — setup, doctor, sync (restore), uninstall, plugin install/update/remove, and the global chain orchestrators. It is the one context the dependency chain lets reach every other context (`framework → translate → tools → kernel`, plus `framework → distribution`), because assembling what goes on disk is exactly the job that needs all three. ## What goes in | Concept | Location | |---|---| | The manifest aggregate and its members | `domain/manifest.ts`, `domain/manifest/` (tool-entry, tracked-files, merge-files, native-registrations) | | A plugin's declared state | `domain/plugins/` (installed-plugin, source-resolver, requested-version-policy) | | The diagnosis shape | `domain/doctor.ts` | | Setup orchestration state | `domain/setup-flow.ts` | | A port only `framework` needs | `domain/ports/` (manifest-repository, plugin-distribution-reader, user-source-references) | | A top-level flow's orchestrator | `application/` root, or a feature subdirectory (`clean/`, `doctor/`, `flows/`, `framework/`, `global/`, `install/`, `plugin/`, `restore/`, `setup/`, `uninstall/`) | | Logic needed by ≥2 top-level use-cases | `application/shared/` — never called from a command | | The manifest-repository and plugin-distribution-reader adapters | `infrastructure/` | ## How
Details
- Skill name
framework- Repository
- ai-driven-dev/framework
- Path
cli/.claude/skills/framework/SKILL.md- License
- MIT
- Repo updated
- 18 November 2026
FAQ
What does the Framework skill do?
Owns the installation record and everything done to a project, under src/contexts/framework/ — the manifest aggregate, and the setup/install/restore/uninstall/doctor orchestration built on top of it. This is the only context allowed to reach `translate` and `distribution`. Use when adding a use-case that touches the manifest, a setup/doctor/sync/uninstall flow, a new top-level CLI orchestration, or a launcher that runs an external binary (kanban-shaped). Do NOT use for a tool's own profile or capability classes — use `tools`. Do NOT use for the translation pipeline — use `translate`. Do NOT us
How do I install the Framework skill?
Claude Code plugin: /plugin marketplace add ai-driven-dev/framework. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Framework popular?
It lives in ai-driven-dev/framework, which has 564 GitHub stars and 65 forks.
Related skills
00 Async Dev
564ai-driven-dev/framework
Drive the async-dev pipeline from one entry point, whether setup, run, or review. Use when the user wants to install async dev, run a ready issue, or address PR review comments, or on a webhook trigger. Not for plain status checks.
00 Init
564ai-driven-dev/framework
Turn AIDD measurement on for a project after explicit consent, stop it, choose to be named on your own measurement, or delete what was measured. Use when the user wants to start or stop measuring what their work consumes, add or remove their name, or forget measured data. Not for answering what a period consumed.
00 Onboard
564ai-driven-dev/framework
Guide a project's journey through AIDD, from first setup to shipping a feature. Use when the user says onboard me, where do I start, or what to do next. Not for listing every installed surface.
Improve Codebase Architecture
211iamyoki/qwen-image-2.1-skill
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
09 Defect
564ai-driven-dev/framework
Produces or refines a backlog Defect from an observed product mismatch. Use when the user wants to report, assess, link, order, transition, or verify a defect. Not for incident response, debugging, or implementation.
Ue Blueprint Cpp Interop
468quodsoler/unreal-engine-skills
Use when exposing C++ to Blueprint or calling Blueprint from C++: UFUNCTION(BlueprintCallable), BlueprintPure, BlueprintImplementableEvent, BlueprintNativeEvent, _Implementation, UBlueprintFunctionLibrary, WorldContext, DefaultToSelf, ExpandEnumAsExecs, DeterminesOutputType, latent nodes, FPendingLatentAction, FLatentActionInfo, UBlueprintAsyncActionBase, BlueprintAssignable, UINTERFACE, Execute_, TScriptInterface, UENUM(BlueprintType), CallInEditor, FindFunction, ProcessEvent. Also use when the user mentions 'expose to Blueprint', 'custom Blueprint node', 'async Blueprint node' or 'meta speci
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.