Brand Guidelines workflow skill. Use this skill when the user needs Write copy following Sentry brand guidelines. Use when writing UI text, error messages, empty states, onboarding flows, 404 pages, documentation, marketing copy, or any user-facing content. Covers both Plain Speech (default) and Sentry Voice tones and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
Brand Guidelines workflow skill. Use this skill when the user needs Write copy following Sentry brand guidelines. Use when writing UI text, error messages, empty states, onboarding flows, 404 pages, documentation, marketing copy, or any user-facing content. Covers both Plain Speech (default) and Sentry Voice tones and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
This public intake copy packages plugins/antigravity-awesome-skills/skills/brand-guidelines from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.
Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.
This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.
Brand Guidelines Write user-facing copy following Sentry's brand guidelines.
Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Tone Selection, Plain Speech (Default), Sentry Voice, Anti-Patterns, Limitations.
When to Use This Skill
Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.
You need to write or rewrite user-facing copy in Sentry's voice.
The task involves UI text, onboarding, empty states, docs, marketing copy, or other branded content.
You need guidance on when to use Plain Speech versus Sentry Voice.
Use when the request clearly matches the imported source intent: Write copy following Sentry brand guidelines. Use when writing UI text, error messages, empty states, onboarding flows, 404 pages, documentation, marketing copy, or any user-facing content. Covers both Plain Speech....
Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
Use when provenance needs to stay visible in the answer, PR, or review packet.
Operating Table
Situation
Start here
Why it matters
First-time use
metadata.json
Confirms repository, branch, commit, and imported path through the external_source block before touching the copied workflow
Provenance review
ORIGIN.md
Gives reviewers a plain-language audit trail for the imported source
Workflow execution
SKILL.md
Starts with the smallest copied file that materially changes execution
Supporting context
SKILL.md
Adds the next most relevant copied source file without loading the entire package
Handoff decision
## Related Skills
Helps the operator switch to a stronger native skill when the task drifts
Workflow
This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.
Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
Read the overview and provenance files before loading any copied upstream support files.
Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
Validate the result against the upstream expectations and the evidence you can point to in the copied files.
Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.
Imported Workflow Notes
Imported: Tone Selection
Choose the appropriate tone based on context:
Use Plain Speech
Use Sentry Voice
Product UI (buttons, labels, forms)
404 pages
Documentation
Empty states
Error messages
Onboarding flows
Settings pages
Loading states
Transactional emails
"What's New" announcements
Help text
Marketing copy
Default to Plain Speech unless the context specifically calls for personality.
Examples
Example 1: Ask for the upstream workflow directly
Use @brand-guidelines-v2 to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.
Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.
Example 2: Ask for a provenance-grounded review
Review @brand-guidelines-v2 against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.
Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.
Example 3: Narrow the copied support files before execution
Use @brand-guidelines-v2 for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.
Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.
Example 4: Build a reviewer packet
Review @brand-guidelines-v2 using the copied upstream files plus provenance, then summarize any gaps before merge.
Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.
Imported Usage Notes
Imported: Dash Usage
Type
Use
Example
Hyphen (-)
Compound words, ranges
"real-time", "1-10"
En-dash (--)
Ranges, relationships
"2023--2024", "parent--child"
Em-dash (---)
Interruption, emphasis
"Errors---even small ones---matter"
In most UI contexts, use hyphens. Reserve en-dashes for date ranges and em-dashes for longer prose.
Best Practices
Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.
Use American English spelling (color, not colour)
Use Title Case for headings and page titles
Use Sentence case for body text, buttons, and labels
No exclamation marks in UI text (exception: celebratory moments)
No periods in short UI labels or button text
Use periods in complete sentences and help text
No ALL CAPS except for acronyms (API, SDK, URL)
Imported Operating Notes
Imported: General Rules
Spelling and Grammar
Use American English spelling (color, not colour)
Use Title Case for headings and page titles
Use Sentence case for body text, buttons, and labels
Punctuation
No exclamation marks in UI text (exception: celebratory moments)
No periods in short UI labels or button text
Use periods in complete sentences and help text
No ALL CAPS except for acronyms (API, SDK, URL)
Word Choices
Avoid
Prefer
Please
(omit)
Sorry
(be specific about the problem)
Error occurred
Something went wrong
Invalid
(explain what's wrong)
Success!
(describe what happened)
Oops
(be specific)
Imported: UI Element Guidelines
Buttons
Use action verbs: "Save", "Delete", "Create"
Be specific: "Create Project" not just "Create"
Max 2-3 words when possible
No periods or exclamation marks
Error Messages
Say what happened
Say why (if helpful)
Say what to do next
Good: "Could not save changes. Check your connection and try again."
Bad: "Error: Save failed."
Empty States
Explain what would normally be here
Provide a clear action to populate the state
Sentry Voice is appropriate here
Good: "No projects yet. Create your first project to start tracking errors."
Confirmation Dialogs
Make the action clear in the title
Explain consequences if destructive
Use specific button labels ("Delete Project", not "OK")
Tooltips and Help Text
Keep under 2 sentences
Explain the "why", not just the "what"
Link to docs for complex topics
Troubleshooting
Problem: The operator skipped the imported context and answered too generically
Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills/skills/brand-guidelines, fails to mention provenance, or does not use any copied source files at all.
Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Check the external_source block first, then restate the provenance before continuing.
Problem: The imported workflow feels incomplete during review
Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task.
Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.
Problem: The task drifted into a different specialization
Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better.
Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.
Related Skills
@00-andruia-consultant - Use when the work is better handled by that native specialization after this imported skill establishes context.
@00-andruia-consultant-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
@10-andruia-skill-smith - Use when the work is better handled by that native specialization after this imported skill establishes context.
@10-andruia-skill-smith-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
Additional Resources
Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.
Resource family
What it gives the reviewer
Example path
references
copied reference notes, guides, or background material from upstream
references/n/a
examples
worked examples or reusable prompts copied from upstream
examples/n/a
scripts
upstream helper scripts that change execution or validation
scripts/n/a
agents
routing or delegation notes that are genuinely part of the imported package
agents/n/a
assets
supporting assets or schemas copied from the source package
