dcode:mine-patterns
npx machina-cli add skill madebynoam/dcode/mine-patterns --openclawMine Patterns
Turn productive sessions into reusable skills.
For designers who think: "I keep doing this same thing... there must be a better way."
Why This Matters
Every time you solve a problem, you're creating a workflow. Most workflows get forgotten. This skill helps you capture the good ones before they disappear.
Instructions
1. Review Session Activities
Look at what was accomplished:
- What tasks were repeated or could be repeated?
- What multi-step workflows were performed?
- What required specific domain knowledge?
- What felt tedious or error-prone?
2. Identify Skill Candidates
Good skills have these traits:
| Trait | Why It Matters |
|---|---|
| Repeatable | Will be done again in future sessions |
| Multi-step | More than a single action |
| Generalizable | Works across different contexts |
| Time-saving | Automates tedious or error-prone work |
| Knowledge-heavy | Requires remembering specific patterns |
3. Categorize by Value
High value - Build these first:
- Complex workflows done frequently
- Tasks where mistakes are costly
- Processes that require specific conventions
Medium value - Build when you have time:
- Useful but less frequent tasks
- Nice-to-have automations
Lower value - Maybe don't bother:
- One-off investigations
- Highly context-specific tasks
4. Present Suggestions
For each potential skill, document:
## Suggested Skill: {name}
**Problem it solves:** {What pain point does this address?}
**Trigger:** {When would someone invoke this?}
**Steps it automates:**
1. {Step 1}
2. {Step 2}
3. {Step 3}
**Value:** High / Medium / Low
**Complexity to build:** Quick (1-2 hrs) / Medium (half-day) / Complex (day+)
5. Help Build the Chosen Skills
If the user wants to create a skill:
- Draft the SKILL.md with proper frontmatter:
---
name: skill-name
description: Clear description of what it does and when to use it
---
- Write clear instructions
- Include examples
- Test it on a real task
Example Output
Based on this session, here are potential skills:
High Value
1. design-token-audit
- Problem: Finding inconsistent colors/spacing across a codebase
- Trigger: "Audit this component for design system compliance"
- Steps: Scan for hardcoded values, compare against tokens, report violations
- Complexity: Medium
2. responsive-check
- Problem: Verifying components work at all breakpoints
- Trigger: Before PR, after styling changes
- Steps: Identify breakpoints, list what changes at each, flag potential issues
- Complexity: Quick
Medium Value
3. figma-to-code-notes
- Problem: Translating design specs into implementation notes
- Trigger: Starting implementation of a new design
- Steps: Extract spacing, colors, typography, create implementation checklist
- Complexity: Medium
Which of these would you like to create?
Meta Note
This skill is itself an example of workflow mining—it was created by noticing that "identifying reusable patterns" was a repeatable, valuable task.
Source
git clone https://github.com/madebynoam/dcode/blob/main/plugins/dcode/skills/mine-patterns/SKILL.mdView on GitHub Overview
Mine Patterns helps you capture repeatable workflows from productive sessions and turn them into reusable skills or commands. It guides you to identify multi-step tasks, categorize their value, and document automation-ready steps so you save time in future tasks.
How This Skill Works
Review your session to spot repeated tasks and multi-step workflows. Identify candidates that are repeatable, generalizable, and time-saving, then categorize them by value. For each candidate, document the problem, trigger, steps, value, and build complexity, optionally drafting a frontmatter-styled SKILL.md when you’re ready to implement.
When to Use It
- After a productive design or coding session where tasks repeat or multi-step workflows emerge.
- When you notice tedious, error-prone steps that recur across projects.
- During retrospectives or post-session reviews to surface automation-worthy workflows.
- Before starting automation work to capture concrete patterns for Claude Code.
- When documenting workflows for reuse across contexts or teams.
Quick Start
- Step 1: Review the session activities to spot repeats and multi-step workflows.
- Step 2: Identify candidate skills using the criteria: repeatable, multi-step, generalizable, time-saving, knowledge-heavy.
- Step 3: Draft each candidate as a suggested skill with Problem, Trigger, Steps, Value, and Complexity; consider creating a SKILL.md frontmatter when ready.
Best Practices
- Capture concrete, repeatable tasks rather than vague ideas.
- Document trigger, steps, and value clearly for each candidate.
- Prioritize high-value, complex workflows first to maximize impact.
- Keep drafts actionable with clearly numbered steps and outcomes.
- Validate by testing on a real task and refine based on results.
Example Use Cases
- design-token-audit — Find inconsistencies in colors/spacing across a codebase.
- responsive-check — Verify components work at all breakpoints.
- figma-to-code-notes — Translate design specs into implementation notes.
- data-cleanup-pipeline — Capture repetitive data-cleanup steps into an automated workflow.
- test-setup-template — Convert recurring test setup steps into a reusable pattern.
