Menu
Use when writing ANY user-facing text -- UI labels, button text, error messages, notifications, tooltips, placeholders, or application content.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when you have an approved design or requirements for a multi-step task, before touching code. Turns designs into implementation plans with bite-sized TDD-oriented tasks, exact file paths, and verification steps. Save to docs/plans/.
Use when starting development work on a bug, feature, improvement, or task. Guides engineers through the full development pipeline: discover, brainstorm, plan, execute, review, ship. Invoked by "let's work on", "I need to build", "fix this bug", "start a new task", or /kickoff.
Use when exploring ideas, comparing approaches, or refining an unclear problem — at any point in the workflow. A discovery-time tool, not a pipeline stage. Invokable directly via /brainstorm or offered by kickoff during DISCOVER. Produces understanding, not artifacts.
Use when you have an implementation plan and want to execute it. Analyzes the plan's task graph, determines the best execution strategy (parallel via team-dev or serial via sdd), and orchestrates the full build with quality gates. The single entry point for plan execution — you don't need to choose between team-dev and sdd yourself.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Enforces root cause investigation through four phases: investigation, pattern analysis, hypothesis testing, and implementation. Prevents guess-and-check thrashing.
Use when creating new skills, specialists, agents, or packs for the Jig framework. Guides the user through an interview to determine what to build, scaffolds the artifact with valid frontmatter, checks for overlap with existing artifacts, and verifies it loads correctly. Triggered by "create a skill", "add a specialist", "extend the framework", or /extend.
| name | eng-copywriting |
| description | Use when writing ANY user-facing text -- UI labels, button text, error messages, notifications, tooltips, placeholders, or application content. |
| tier | standards |
| alwaysApply | true |
PURPOSE: Ensure consistent sentence case formatting across all user-facing content.
ALL user-facing text uses sentence case -- capitalize only the first word and proper nouns.
Sentence case (USE THIS) Title Case (NEVER)
------------------------------------------------------
Create component Create Component
Save changes Save Changes
No results found No Results Found
Edit API key Edit API Key
Failed to load data Failed to Load Data
| Capitalize | Examples |
|---|---|
| First word | "Create component", "Save changes" |
| Acronyms | API, URL, PDF, YAML, SSO, ID, CSV, JSON, XML, HTML |
| Product names | Google, Microsoft, GitHub, Slack, AWS, Docker |
| Proper nouns | Company names, person names, place names |
Examples across different contexts:
-- Buttons and Actions --
Save changes (not "Save Changes")
Create new item (not "Create New Item")
Sign in with Google (not "Sign In With Google")
Export as CSV (not "Export As CSV")
-- Page Titles and Headings --
Account settings (not "Account Settings")
API key created (not "API Key Created")
Recent activity (not "Recent Activity")
-- Error Messages --
Failed to load data (not "Failed to Load Data")
Something went wrong (not "Something Went Wrong")
File not found (not "File Not Found")
-- Tooltips and Placeholders --
Search by name (not "Search By Name")
Enter your email (not "Enter Your Email")
No results found (not "No Results Found")
| Mistake | Fix |
|---|---|
| "Add New Item" | "Add new item" |
| "View All Components" | "View all components" |
| "Error Loading Data" | "Error loading data" |
| "Successfully Saved!" | "Successfully saved!" |
| "Are You Sure?" | "Are you sure?" |
| "Select A Template" | "Select a template" |
| "Go To Dashboard" | "Go to dashboard" |
| "Sign Up For Free" | "Sign up for free" |
Exception: Acronyms stay uppercase even mid-sentence: "Edit API key", "Upload CSV file", "Enter URL"
This standard applies to ALL user-facing text regardless of framework, language, or platform:
When in doubt, read the text out loud. If it sounds like a newspaper headline, it's probably title case -- fix it.