From working-style
Use when user has vague idea, rough concept, or unclear requirements for building an application. Triggers on "I want to build", "help me create", "make a thing that", unclear scope, missing constraints, or when prompts lack explicit requirements.
How this skill is triggered — by the user, by Claude, or both
Slash command
/working-style:prompt-architectThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Transform rough application ideas into explicit, buildable prompts for Claude Code.
Transform rough application ideas into explicit, buildable prompts for Claude Code.
Core principle: Vague prompts produce vague results. This skill extracts hidden assumptions, surfaces missing requirements, and generates structured prompts that Claude Code can execute without guesswork.
digraph when_to_use {
"User provides idea" [shape=doublecircle];
"Is it already explicit?" [shape=diamond];
"Missing 2+ of: users, stack, scale, constraints?" [shape=diamond];
"Skip this skill" [shape=box];
"Use prompt-architect" [shape=box];
"User provides idea" -> "Is it already explicit?";
"Is it already explicit?" -> "Skip this skill" [label="yes - clear requirements"];
"Is it already explicit?" -> "Missing 2+ of: users, stack, scale, constraints?" [label="no - vague"];
"Missing 2+ of: users, stack, scale, constraints?" -> "Use prompt-architect" [label="yes"];
"Missing 2+ of: users, stack, scale, constraints?" -> "Skip this skill" [label="no - minor gaps"];
}
Use when:
Skip when:
Extract from user input:
| Dimension | 1 (Simple) | 3 (Medium) | 5 (Complex) |
|---|---|---|---|
| Features | Single purpose | 3-4 features | 5+ interconnected |
| Integrations | Standalone | 1-2 services | Multiple APIs |
| Data | No persistence | Simple storage | Complex schema |
| Users | Single/CLI | Basic multi-user | Roles, real-time |
| Deployment | Local script | Single service | Distributed |
Overall = average of applicable dimensions.
Check for missing critical info:
If more than 2 gaps affect architecture:
Select template by complexity score:
## Task
[One clear sentence]
## Requirements
- [Explicit requirement 1]
- [Explicit requirement 2]
## Constraints
- [Technical constraint]
- [Environmental constraint]
## Success Criteria
- [Measurable outcome 1]
- [Measurable outcome 2]
## Context
[Problem, why it matters, who benefits - 2-3 sentences]
## Requirements
### Functional
- [What system must do]
- [Key user interactions]
### Non-Functional
- [Performance]
- [Security]
- [UX/DX]
## Architecture
### Components
- **[Component]**: [Responsibility]
### Data Flow
[Inputs -> Processing -> Outputs]
## Tech Decisions
- **[Category]**: [Choice] - [Rationale]
## Implementation Order
1. [Foundation]
2. [Next step]
3. [Continue...]
## Edge Cases
- [What could break] -> [How to handle]
## Context
[Problem, business value, users, success metrics]
## Requirements
### Functional
[Numbered list with acceptance criteria]
### Non-Functional
- **Performance**: [Latency, throughput targets]
- **Scalability**: [Growth expectations]
- **Security**: [Auth, compliance]
- **Reliability**: [Uptime, failure handling]
## System Architecture
### Components
[Each with responsibility]
### Interactions
[Sync/async, protocols, contracts]
### Data Architecture
- **Storage**: [Choices, rationale]
- **Schema**: [Key entities]
- **Flow**: [Transforms, persistence]
### API Contracts
[Key endpoints with shapes]
## Tech Stack
| Layer | Choice | Rationale |
|-------|--------|-----------|
## Implementation Phases
### Phase 1: Foundation
- [Core infrastructure]
- **Milestone**: [What works]
### Phase 2: Core Features
- [Primary features]
- **Milestone**: [What works]
### Phase 3: Polish
- [Optimization, additional features]
- **Milestone**: [Production ready]
## Testing Strategy
- **Unit**: [What to test]
- **Integration**: [Key points]
- **E2E**: [Critical journeys]
## Risks
| Risk | Impact | Mitigation |
|------|--------|------------|
## Open Questions
[Decisions needing input]
| Mistake | Fix |
|---|---|
| Accepting "build X" without clarification | Always identify gaps first |
| Over-engineering simple ideas | Match template to complexity score |
| Leaving tech decisions open | Make opinionated recommendations |
| Ignoring non-functional requirements | Always include performance, security, errors |
| Generating abstract architecture | Every component needs concrete responsibility |
| Skipping edge cases | Explicitly list failure modes |
/prompt-architect "slack bot that queries our postgres database"
## Context
Slack bot enabling non-technical team to query business data via natural language,
reducing dependency on engineers for ad-hoc reports.
## Requirements
### Functional
- NL query via slash command or mention
- LLM translates to SQL
- Execute on read-only Postgres replica
- Formatted results in Slack (tables, simple charts)
- Query history per user
### Non-Functional
- Response < 5s for typical queries
- SQL injection prevention (parameterized, validated)
- Rate limiting per user
- Audit logging all queries
## Architecture
### Components
- **Slack App**: Receives commands, sends responses
- **Query Service**: NL->SQL, validation, execution
- **Postgres Replica**: Read-only query target
### Data Flow
User -> Slack API -> Query Service -> LLM -> Validation -> Postgres -> Format -> Slack
## Tech Decisions
- **Runtime**: Node.js - Good Slack SDK
- **LLM**: Claude API - Strong SQL generation
- **Hosting**: AWS Lambda - Cost-effective for bursty traffic
## Implementation Order
1. Slack app with slash command handler
2. LLM integration for SQL generation
3. Postgres read-only connection
4. Result formatting
5. Validation layer
6. Rate limiting + audit logging
## Edge Cases
- Invalid SQL -> Reject with explanation
- Query timeout -> Cancel + notify
- Large results -> Paginate or summarize
- Slack API failure -> Retry with backoff
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
npx claudepluginhub mhardist/claude-context-harness --plugin working-style