devdocs
Skill0 starsChanged 43 days agoNo licenceView on GitHub
Captures reusable engineering knowledge from completed Shopify theme development tasks in Asana (task discussion + linked GitHub PR) and turns it into searchable, structured client documentation stored in Google Drive. Also loads that documentation back into the current Claude Code session before new related work starts, so past fixes, known Shopify limitations, workarounds, and codebase architecture don't get rediscovered from scratch. Use this skill whenever the user asks to document a completed task, log a fix, save what was learned from a PR, turn an Asana task into documentation, or wants prior knowledge loaded for a client before starting work (e.g. "get-context for Ruti", "what do we know about this client's theme", "load context", "document this task"). Shared, cross-client docs under shopify-theme/shared/ are only ever written via the explicit "/devdocs update/shopify-theme/shared" invocation, never automatically during capture. Also trigger on the bare skill name or shorthand like "/devdocs" or "/devdocs get-context/..." or "/devdocs update/...".
In this repository2 other files it gives its agents.
- lets-workSkill
- test-changesSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 3 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.