design-partner

Maintains a discussion-only posture for design brainstorming and architecture tradeoff analysis.

2|Updated May 13, 2026
One-click install
npx skills add https://github.com/curtisgalloway/public-skills --skill design-partner-curtisgalloway
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-partner
Source: https://github.com/curtisgalloway/public-skills/tree/main/plugins/agent-workflow/skills/design-partner
Command: npx skills add https://github.com/curtisgalloway/public-skills --skill design-partner-curtisgalloway

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding agents tend to drift toward action: during a design discussion they start planning edits and making changes before the user has finished thinking. This Skill holds a thinking-partner posture for an entire session, so brainstorming stays brainstorming until the user explicitly asks to build. ## Core Features & Use Cases - Sticky no-action mode: Blocks file edits, state-changing commands, and implementation code while active, while still allowing code reading to ground the discussion. - Structured reasoning style: Explains reasoning before conclusions, presents at least two options with concrete tradeoffs before recommending, and pushes back on weak premises with specifics. - Explicit exit condition: The mode ends only when the user signals build intent, then offers to capture the converged design as a written plan or spec. - Use Case: You are deciding between two database schemas for a new feature. Activate the mode, explore tradeoffs over several turns without any code being touched, then say "let's implement" to transition into execution with a captured spec. ## Quick Start Ask the agent to act as a design partner and talk through the tradeoffs of your architecture decision without making any code changes.

Frequently Asked Questions about design-partner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I brainstorm architecture with an AI agent without it writing code?▼

Activate a design-partner mode that explicitly forbids file edits and state-changing commands while active. The agent reads code to ground the discussion but only describes proposed changes instead of applying them until you signal build intent.

How do I get an AI to present tradeoffs instead of one recommendation?▼

Instruct the agent to lay out at least two approaches, each with what it concretely optimizes for and what it gives up, before giving a recommendation. This lets you disagree with the reasoning rather than just the conclusion.

When does design discussion mode end and coding begin?▼

The mode ends only when you explicitly signal build intent, such as saying "let's implement" or providing a concrete spec to execute. It does not end merely because the discussion feels settled, preventing premature edits.

Can the agent still read my code during a design discussion?▼

Yes, reading code to ground the discussion is allowed and encouraged. Only edits, state-changing commands, and writing implementation code are blocked while the mode is active.

What happens to the design after the discussion ends?▼

On exit, the agent offers to capture the converged design as a written plan or spec. This carries the thinking cleanly into implementation without forcing documentation you do not want.