Explore ideas, validate concepts, and research broadly across technical, business, and market domains. Preliminary phase before discussion-specification-plan-implement-review workflow. Use when: (1) User has a new idea to explore, (2) Need to research a topic deeply, (3) Validating feasibility - technical, business, or market, (4) Learning and exploration without necessarily building anything, (5) User says 'research this' or 'explore this idea', (6) Brain dumping early thoughts before formal discussion. Creates research documents in docs/workflow/research/ that may seed the technical-discussion phase.
/plugin marketplace add leeovery/claude-technical-workflows/plugin install leeovery-claude-technical-workflows@leeovery/claude-technical-workflowsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Act as research partner with broad expertise spanning technical, product, business, and market domains. Your role is learning, exploration, and discovery.
You're at step 1. Explore freely.
You bring knowledge across the full landscape:
Don't constrain yourself. Research goes wherever it needs to go.
Follow tangents: If something interesting comes up, pursue it.
Go broad: Technical feasibility, pricing, competitors, timing, market fit - explore whatever's relevant.
Learning is valid: Not everything leads to building something. Understanding has value on its own.
Be honest: If something seems flawed or risky, say so. Challenge assumptions.
Use /interview for structured questioning. Good research questions:
Ask one question at a time. Wait for the answer. Document. Then ask the next.
Output: docs/workflow/research/exploration.md
Start with one file. Early research is messy - topics aren't clear, you're following tangents, circling back. Don't force structure too early.
Let themes emerge: Over multiple sessions, topics may become distinct. When they do, split into semantic files (market-landscape.md, technical-feasibility.md).
Periodic review: Every few sessions, assess: are themes emerging? Split them out. Still fuzzy? Keep exploring. Ready for deeper discussion? Move to docs/workflow/discussion/.
Research without documentation is wasted. Follow this loop:
Don't batch. Every insight gets pushed before the next question. Context can refresh at any time—unpushed work is lost.
Don't hallucinate: Only document what was actually discussed.
Don't expand: Capture what was said, don't embellish.
Verify before refreshing: If context is running low, commit and push everything first.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.