Results for “directory-structure”

10 skills
More results
github
Folder Structure Blueprint Generator
Analyzes project folder structures, auto-detects technology stacks, and generates detailed blueprints with naming conventions, file placement patterns, and templates for consistent code organization.
36.2k
tradermonty
Skill Designer
Generates a structured Claude CLI prompt from a JSON idea specification to bootstrap a complete skill directory with SKILL.md, references, scripts, and tests following repository conventions.
2.3k · bundle
seb1n
File Organization
Automatically organizes files in a directory into a clean structure based on configurable rules — by file type, date, project, or priority — with support for duplicate detection, naming conventions, and archival strategies. Use when the user requests file organization or provides relevant inputs for this workflow.
159
composiohq
File Organizer
Analyzes file systems to find duplicates, suggest folder structures, and automate cleanup tasks with user approval.
66.9k
ecnu-icalk
File Organizer
Organizes files and folders by analyzing structure, finding duplicates, and proposing logical groupings, with user approval before any changes.
559
b4san
Acfm Spec Workflow
Initialize and manage AC Framework spec-driven workflows using acfm CLI. Use when setting up spec workflows, checking project status, creating changes, or understanding the .acfm/ vs openspec/ directory structures. Essential first step before using any OpenSpec skills.
2
jasoncarreira
Chainlink
Local CLI issue tracker for todos, follow-ups, structured records, and the canonical pattern for decomposing multi-step work into a parent + subissues with acceptance criteria, dependency edges, and priority. Use when the user mentions a task to remember, a bug to track, an open question, anything that needs to outlive the current turn, or when planning multi-heartbeat work that needs `chainlink issue ready`-driven pickup across sessions. Includes guidance on writing descriptions future-you can act on (handles, success path, failure path) and idempotency tactics for actions that might fire twice (boundary firing, overlapping heartbeats, retried subagent completion). Pairs with five-whys (chainlink is the storage backend for RCA trees). Storage is local — issues live under a `.chainlink/` directory in the operator's repo.
6 · bundle