design-workflow
Design Workflow Skill
Guidelines for making UI designs that don't look AI-generated. These rules apply to any design work — prototypes, design docs, or UI code.
What This Skill Does
- Teaches how to avoid "generic AI" design patterns
- Provides a checklist for design quality
- Guides component-by-component design approach
- Sets prototype quality standards
Rule 1: Use the Existing Design System
NEVER invent new colors, fonts, or spacing. Always use what the project defines.
What to Read FIRST
.planning/design-config.md— project colors, fonts, spacing, brand identity- The theme files listed in design-config — actual CSS tokens
- Existing components in the codebase — match their patterns
More from spartan-stratos/spartan-ai-toolkit
kotlin-best-practices
Kotlin coding standards including null safety, Either error handling, coroutines, and Exposed ORM patterns. Use when writing Kotlin code, reviewing code quality, or learning project patterns.
11ops-investigate-alert
Investigate a monitoring alert end-to-end. Pulls metrics, logs, traces, and recent code changes to identify root cause. Works with any monitoring MCP.
10startup-pipeline
Coordinates the full startup idea pipeline from brainstorm to investor outreach. Use when the user starts a new idea project, asks for the 'full pipeline', or references stages/gates.
9terraform-service-scaffold
Generate complete service-level Terraform infrastructure with modules, environments, and CI/CD. Use when adding Terraform to a new service or bootstrapping infrastructure from scratch.
8investor-outreach
Draft cold emails, warm intro blurbs, follow-ups, and investor communications. Use when the user needs to write to angels, VCs, or accelerators.
8article-writing
Write blog posts, guides, tutorials, and long-form content. Sounds like a real person, not AI. Use when the user wants polished written content.
8