2.5k
GitHub Stars
4
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill openclaw/skills --skill extraction- _meta.json277 B
- COMMAND.md2.5 KB
- README.md660 B
- SKILL.md9.9 KB
Overview
This skill extracts design systems, architecture patterns, and methodology from existing codebases and turns them into reusable skills and documentation. It captures tokens, UI and architecture patterns, build workflows, and the aesthetic direction so teams can reuse proven decisions. Use it to document how a project is built and to generate project-agnostic skills that encode repeatable patterns.
How this skill works
The extraction runs in discovery, categorization, extraction, validation, and output phases. It scans the repo for structure, config files, theme and CSS files, workflows, and documentation, then maps findings into priority categories (design systems, UI patterns, architecture, workflows, domain-specific). For each valuable pattern it produces a documentation file and a reusable skill artifact, validates quality criteria, and stages outputs for refinement.
When to use it
- Analyze a repo to capture its design tokens and aesthetic direction
- Create reusable skills from recurring UI or architecture patterns
- Document project build and deployment workflows for onboarding
- Archive and standardize patterns found across multiple projects
- Audit a codebase to identify reusable, intentional configurations
Best practices
- Prioritize extracting intentional, reused patterns over defaults or one-offs
- Always capture actual token values (colors, typography, spacing) rather than placeholders
- Validate each extracted skill against a quality checklist before publishing
- Keep extracted skills project-agnostic and avoid hardcoded project names
- Document gaps and incomplete extractions clearly for later refinement
Example use cases
- Extract a Tailwind-based design system: color palette, spacing scale, and typography tokens
- Turn a recurring dashboard component pattern into a reusable skill with usage notes
- Summarize a microservice repo’s architecture and data flow for onboarding docs
- Capture CI/CD and Docker workflow commands into a concise developer setup doc
- Stage extracted patterns from several archived projects for consolidation
FAQ
It produces extract documentation for design systems and project summaries, and a set of reusable skill artifacts that encode discovered patterns and usage guidance.
How do you avoid duplicate or low-value skills?
The process checks existing skills for overlap, skips default or one-off solutions, and applies a value filter to extract only intentional, widely used patterns.