pattern-extraction
Extract design systems, architecture patterns, and methodology from codebases into reusable skills and documentation. Use when analyzing a project to capture patterns, creating skills from existing code, extracting design tokens, or documenting how a project was built. Triggers on "extract patterns", "extract from this repo", "analyze this codebase", "create skills from this project", "extract design system".
Why use this skill?
Automate codebase analysis with the OpenClaw pattern-extraction skill. Discover design systems, architectural patterns, and methodologies to create reusable AI skills.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/wpank/extractionWhat This Skill Does
The pattern-extraction skill is a sophisticated analysis tool designed for OpenClaw agents to parse complex codebases and distill them into reusable assets. It systematically crawls project repositories to identify design systems, architectural patterns, and development methodologies. By automating the extraction process, this skill allows teams to standardize their tech stacks, document tribal knowledge, and convert scattered code components into formal, reusable OpenClaw skills.
Installation
To install this skill, run the following command in your terminal:
npx clawhub@latest install extraction
Ensure that you have your OpenClaw environment initialized before running the installation command. This will register the extraction workflows in your project's skills/ directory.
Use Cases
- Design System Extraction: Automatically pull design tokens, Tailwind configurations, and UI components from a mature project to jumpstart a new design system.
- Architecture Documentation: Generate comprehensive documentation of data flow, folder structures, and API patterns, ensuring that new developers can quickly understand the project's foundational decisions.
- Skill Generation: Identify recurring logic, such as authentication handlers or custom validation hooks, and convert them into isolated, testable OpenClaw skills for future automation tasks.
- Legacy Refactoring: Extract patterns from aging codebases to distinguish between critical business logic and technical debt that can be safely discarded during modernization.
Example Prompts
- "Extract patterns from this repo and identify the core UI design system components used in the dashboard."
- "Analyze this codebase to create a new skill that mimics our existing authentication flow architecture."
- "Extract design system tokens and typography from the current tailwind config and document them in a formal style guide."
Tips & Limitations
- Mandatory References: Always review
methodology-values.mdbefore starting an extraction to ensure the agent understands your project's specific priorities. - Context Quality: The accuracy of the extraction is heavily dependent on the clarity of your existing codebase. Projects with well-defined directory structures and documented comments yield significantly higher-quality skills.
- Manual Review: While this skill automates the discovery process, always perform a final audit of the generated documentation, especially when extracting infrastructure-level patterns, as context-specific hacks may be erroneously flagged as reusable patterns.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-wpank-extraction": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: file-read, file-write
Related Skills
mermaid-diagrams
Create software diagrams using Mermaid syntax. Use when users need to create, visualize, or document software through diagrams including class diagrams, sequence diagrams, flowcharts, ERDs, C4 architecture diagrams, state diagrams, git graphs, and other diagram types. Triggers include requests to diagram, visualize, model, map out, or show the flow of a system.
api-design-principles
Skill by wpank
auto-context
Automatically read relevant context before major actions. Loads TODO.md, roadmap.md, handoffs, task plans, and other project context files so the AI operates with full situational awareness. Use when starting a task, implementing a feature, refactoring, debugging, planning, or resuming a session.
clear-writing
Write clear, concise prose for humans — documentation, READMEs, API docs, commit messages, error messages, UI text, reports, and explanations. Combines Strunk's rules for clearer prose with technical documentation patterns, structure templates, and review checklists.
track-performance
Track the performance of Uniswap LP positions over time — check which positions need attention, are out of range, or have uncollected fees. Use when the user asks how their positions are doing.