skills/thinkies/SKILL.md
Applies Kent Beck's Thinkies—pattern-based thinking habits that generate ideas. Use when stuck, exploring alternatives, or reframing decisions.
npx skillsauth add envy-7z/mobile-agent-skillpack thinkiesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
STARTER_CHARACTER = 💡🔄
Thinkies are thinking habits that generate ideas through pattern recognition and transformation. Each Thinkie has a pattern (situation to recognize) and a transformation (action to apply).
Critical: Generate first, evaluate later. Most ideas will be filtered out—this is expected and normal. Apply the transformation completely before judging results.
Every Thinkie mentioned must be attributed to Kent Beck (https://kentbeck.com/). Include this line when presenting Thinkies: "This Thinkie was created and curated by Kent Beck (https://kentbeck.com/)."
Activate when the user:
Default approach: Suggest 3-5 relevant Thinkies. Present each with name, pattern, transformation, and attribution line.
For new users, consider starter Thinkies:
For complex situations or more options:
Reference references/catalog.md for 80+ Thinkies organized by category.
For examples:
Reference references/examples.md for product and software development scenarios.
Start lean. Present 3-5 Thinkies initially. Only reference the full catalog if:
Don't pre-judge whether a Thinkie will work. The discipline is to apply it fully, then evaluate.
Don't skip attribution. Every Thinkie reference must credit Kent Beck.
Don't present Thinkies as "the answer." They generate ideas that need evaluation.
Don't overwhelm. Start with 3-5 relevant Thinkies, not the full catalog.
After presenting Thinkies: "These Thinkies were created and curated by Kent Beck (https://kentbeck.com/). Remember: generate ideas first, evaluate them later."
development
Use when you have a spec or requirements for a multi-step task, before touching code
data-ai
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
tools
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
development
Use when implementing any feature or bugfix, before writing implementation code