constraint-based-creativity
$
npx mdskill add lyndonkl/claude/constraint-based-creativityTransforms limitations into novel solutions for creative blocks.
- Helps brainstorm when ideas feel stuck or repetitive.
- Integrates with any brainstorming or design workflow.
- Decides constraints by analyzing user context and keywords.
- Delivers structured creative strategies with clear examples.
SKILL.md
.github/skills/constraint-based-creativityView on GitHub ↗
--- name: constraint-based-creativity description: Turns limitations into creative fuel by strategically imposing constraints that force novel thinking, break habitual patterns, and reveal unexpected solutions. Covers resource constraints (budget/time/tools), format constraints (length/medium), rule-based constraints, and perspective constraints. Use when brainstorming feels stuck or generates obvious ideas, working with limited resources, designing with specific limitations, or when user mentions "think outside the box", "we're stuck", "same old ideas", "tight constraints", or "limited budget/time". --- # Constraint-Based Creativity ## Table of Contents - [Overview](#overview) - [Workflow](#workflow) - [Constraint Types](#constraint-types) - [Common Patterns](#common-patterns) - [Guardrails](#guardrails) - [Quick Reference](#quick-reference) ## Overview Deliberately limiting freedom (resources, rules, materials, format) paradoxically boosts creativity by reducing decision paralysis, breaking habitual patterns, forcing novel combinations, and creating memorable differentiation. **Quick example:** Twitter's original 140-character limit forced concise, punchy writing. Haiku's 5-7-5 syllable structure produces poetry. $10K budget forces guerrilla marketing over Super Bowl ads. Building with only CSS (no images) creates distinctive visual style. ## Workflow Copy this checklist and track your progress: ``` Constraint-Based Creativity Progress: - [ ] Step 1: Understand the problem and context - [ ] Step 2: Choose or design strategic constraints - [ ] Step 3: Generate ideas within constraints - [ ] Step 4: Evaluate and refine solutions - [ ] Step 5: Validate quality and deliver ``` **Step 1: Understand the problem and context** Ask user for the creative challenge (what needs solving), current state (what's been tried, why it's not working), ideal outcome (success criteria), and any existing constraints (real limitations already in place). Understanding why ideas feel stale or stuck helps identify which constraints will unlock creativity. See [Constraint Types](#constraint-types) for strategic options. **Step 2: Choose or design strategic constraints** If user has existing constraints (tight budget, short timeline, limited materials) → Use [resources/template.md](resources/template.md) to work within them creatively. If no constraints exist and ideation is stuck → Study [resources/methodology.md](resources/methodology.md) to design strategic constraints that force new thinking patterns. Choose 1-3 constraints maximum to avoid over-constraining. **Step 3: Generate ideas within constraints** Apply chosen constraints rigorously during ideation. Create `constraint-based-creativity.md` file documenting: problem statement, active constraints (what's forbidden/required/limited), idea generation process, and all ideas produced (including "failed" attempts that revealed insights). Quantity matters - aim for 20+ ideas before evaluating. See [resources/template.md](resources/template.md) for structured generation process. **Step 4: Evaluate and refine solutions** Assess ideas using dual criteria: (1) Does it satisfy all constraints? (2) Does it solve the original problem? Select strongest 2-3 ideas. Refine by combining elements, removing unnecessary complexity, and strengthening the constraint-driven insight. Document why certain ideas stand out - often the constraint reveals an unexpected angle. See [resources/methodology.md](resources/methodology.md) for evaluation frameworks. **Step 5: Validate quality and deliver** Self-assess using [resources/evaluators/rubric_constraint_based_creativity.json](resources/evaluators/rubric_constraint_based_creativity.json). Verify: constraints were genuinely respected (not bent/broken), solutions are novel (not slight variations of existing), the constraint created the creativity (solution wouldn't exist without it), ideas are actionable (not just conceptual), and creative insight is explained (why this constraint unlocked this idea). Minimum standard: Average score ≥ 3.5. Present completed `constraint-based-creativity.md` file highlighting the constraint-driven breakthroughs. ## Constraint Types Strategic constraints fall into categories. Choose based on what pattern you want to break: **Resource Constraints** (force efficiency): - Budget: "Design this campaign for $500" (vs typical $50K) - Time: "Ship in 48 hours" (vs typical 2-week sprint) - Team: "Solo project only" or "No engineers" - Materials: "Found objects only" or "Recyclables only" **Format/Medium Constraints** (force adaptation): - Length: "Explain in 10 words" or "Story in 6 words" - Medium: "Text only, no images" or "Visual only, no words" - Platform: "Twitter thread only" (vs blog post) - Dimensions: "Square format only" or "Vertical video" **Rule-Based Constraints** (force creative workarounds): - Forbidden elements: "No letter 'e'" or "No adjectives" - Required elements: "Must include these 3 objects" - Style rules: "Hemingway style only" or "As if Shakespeare" - Process rules: "No editing, one-take only" **Technical Constraints** (force optimization): - Code: "100 lines maximum" or "No external libraries" - Performance: "Load in <1 second" or "Run on 1990s hardware" - Data: "No PII collection" or "Works offline" - Compatibility: "Text-based only (ASCII art)" **Audience/Perspective Constraints** (force reframing): - Audience: "Explain to 5-year-olds" or "For experts only" - Perspective: "First person only" or "Second person only" - Tone: "No corporate speak" or "Casual only" - Voice: "Write as [specific person/character]" ## Common Patterns **Pattern: The Limitation Sprint** When team is stuck, run 30-minute sprints with different constraints. Example: "10 ideas using only free tools" → "10 ideas in black/white only" → "10 ideas for $100 budget." Constraint rotation prevents pattern fixation. **Pattern: The Subtraction Game** Remove assumed "essentials" one at a time. Example: "App without login" → "App without UI" (voice only) → "App without internet" (offline-first). Forces questioning assumptions. **Pattern: The Format Flip** Change medium to force different thinking. Example: "Explain strategy as a recipe" or "Present roadmap as a movie trailer" or "Write documentation as a children's book." **Pattern: The Resource Inversion** Make the assumed limitation the focus. Example: "We have no budget" → "Build guerrilla marketing campaign showcasing zero-budget creativity" or "Only 2-person team" → "Sell the 'small team, big care' advantage." **Pattern: The Historical Constraint** Impose constraints from different eras. Example: "Design this as if it's 1995" (pre-smartphone) or "Build this with Victorian-era materials" or "Market this like 1960s Mad Men." ## Guardrails **✓ Do:** - Choose constraints that directly counter the creative block (stuck on complexity → simplicity constraint) - Enforce constraints rigorously during ideation (no "bending" rules mid-process) - Generate high volume before judging (quantity first, then quality) - Document failed ideas - they often contain seeds of insight - Explain how the constraint created the solution (causality matters) - Use multiple different constraints in sequence (sprint pattern) **✗ Don't:** - Over-constrain (3+ simultaneous constraints usually paralyzes) - Choose arbitrary constraints unrelated to the problem - Abandon constraints when ideas get hard (that's when breakthroughs happen) - Confuse constraint-based creativity with regular brainstorming - Accept slight variations of existing ideas (constraint should force novelty) - Skip the evaluation step (need to validate constraint drove the creativity) ## Quick Reference **Resources:** - `resources/template.md` - Structured process for generating ideas within constraints - `resources/methodology.md` - Advanced techniques for designing strategic constraints, combining constraint types, and systematic exploration - `resources/examples/` - Worked examples showing constraint-driven breakthroughs - `resources/evaluators/rubric_constraint_based_creativity.json` - Quality assessment before delivery **When to choose which resource:** - Working with existing constraints (budget, time, technical) → Start with template - No constraints but ideation is stuck → Study methodology to design constraints - Need to see examples of breakthroughs → Review examples folder - Before delivering to user → Always validate with rubric **Expected deliverable:** `constraint-based-creativity.md` file containing: problem statement, chosen constraints with rationale, idea generation process (including volume metrics), top 2-3 solutions with refinement notes, explanation of how constraints drove creativity, and next steps.
More from lyndonkl/claude
- abstraction-concrete-examplesBuilds structured abstraction ladders that translate high-level principles into concrete, actionable examples across 3-5 levels. Bridges communication gaps, reveals hidden assumptions, and tests whether abstract ideas work in practice. Use when explaining concepts at different expertise levels, moving between abstract principles and concrete implementation, identifying edge cases by testing ideas against scenarios, designing layered documentation, decomposing complex problems into actionable steps, or bridging strategy-execution gaps.
- academic-letter-architectGuides the creation of evidence-based academic recommendation letters, reference letters, and award nominations that combine concrete examples, meaningful comparisons, and genuine enthusiasm. Use when writing recommendation letters for students, postdocs, or colleagues, or when user mentions recommendation letter, reference, nomination, letter of support, endorsement, or needs help with strong advocacy and comparative statements.
- adr-architectureDocuments significant architectural and technical decisions with full context, alternatives considered, trade-offs analyzed, and consequences understood. Creates a decision trail that helps teams understand why decisions were made. Use when choosing between technology options, making infrastructure decisions, establishing standards, migrating systems, or when user mentions ADR, architecture decision, technical decision record, or decision documentation.
- adverse-selection-priorProduces a Bayesian prior probability that an offered transaction is +EV for the recipient, given that the counterparty chose to propose it. Applies Akerlof market-for-lemons logic -- if they offered it, they believe it is +EV for them, so the prior that it is +EV for us is materially below 50%. Reusable across trade evaluation, waiver drops (another team dropping a player is also adverse selection), job-offer analysis, M&A, and any "someone offered me this" situation. Use when you receive an unsolicited trade/offer/proposal, analyzing incoming trade prior, evaluating why a counterparty proposed a deal, or when user mentions adverse selection, market for lemons, why did they offer this, incoming trade prior, they proposed it, Bayesian adjustment on received offer.
- alignment-values-north-starCreates actionable alignment frameworks that give teams a shared North Star (direction), values (guardrails), and decision tenets (behavioral standards). Enables autonomous decision-making while maintaining organizational coherence. Use when starting new teams, scaling organizations, defining culture, establishing product vision, resolving misalignment, creating strategic clarity, or when user mentions North Star, team values, mission, principles, guardrails, decision framework, or cultural alignment.
- analogy-weight-checkFor every analogy in a substacker draft, verifies it carries mechanical weight — the analogy does real work explaining the mechanism, not merely decorates it. Cross-references analogy-catalog.md for novelty (is this analogy reused from a prior post?) and domain fit (biology > organizational > sports preferred; physics/military disfavored). Use whenever an analogy appears in the draft. Trigger keywords: analogy weight, decorative, mechanical weight, reused analogy, catalog check, metaphor check.
- answer-uncomfortable-questionTakes one strategic question about substacker ("should we launch paid?", "is this section dead?", "are we writing for the wrong audience?") and produces the mandatory evidence + reasoning + downside triad plus a recommendation. Used 3 times per Growth Strategist review. Trigger keywords: uncomfortable question, strategic question, evidence reasoning downside, triad.
- attribute-performanceFor each substacker post that materially over- or under-performs the rolling baseline (|z| ≥ 1.0), produces a plain-English attribution paragraph with calibrated confidence (high / medium / low / unexplained). Considers subject-line effect, topic zeitgeist, external share, day-of-week, length effect, and audience-notes signals. Labels unexplained outliers explicitly rather than fabricating a story. Use after compute-baseline when outlier posts exist. Trigger keywords: attribution, why did this post work, outlier explanation, performance analysis.
- auction-first-price-shadingComputes the optimal shaded bid for a first-price sealed-bid auction given a true private value, an estimate of the number of competing bidders N, and a value-distribution assumption. Implements the `(N-1)/N` equilibrium shading rule for uniform private values, adjusts for log-normal or empirical value distributions, layers a risk-aversion adjustment, and caps output against the bidder's remaining budget. Domain-neutral auction theory reusable across fantasy sports (baseball FAAB, NBA/NHL waiver auctions), prediction-market limit sizing, sealed procurement bids, and any blind-bid context. Use when user mentions "first-price auction bid", "sealed bid shading", "(N-1)/N", "FAAB bid amount", "auction shading", "optimal bid first-price", "bid for sealed-bid", "blind bid sizing", or when downstream logic needs a principled shade factor rather than an ad-hoc heuristic.
- auction-winners-curse-haircutApplies a Bayesian haircut to a bid valuation for common-value auctions where winning is itself evidence the bidder over-estimated. Takes a raw valuation, a value-type classification (common_value / private_value / mixed), the number of informed bidders N, and a signal-dispersion estimate, and returns an adjusted valuation. Domain-neutral and reusable across fantasy FAAB, prediction markets, M&A bids, ad-auction budgets, and any generic bidding context. Use when user mentions "winner's curse", "common value auction", "valuation haircut", "adverse valuation", "Bayesian bid adjustment", or "over-paying in auction".