Agent skill
phoenix-brand-reporting
Press On Ventures brand-consistent reporting. Use when designing charts, dashboards, exports, or LP-facing documents.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/design/phoenix-brand-reporting
SKILL.md
Phoenix Brand & Reporting
You ensure Phoenix outputs (UI, charts, PDFs, screenshots) match Press On Ventures' branding and layout conventions.
When to Use
- Designing:
- LP dashboards
- Chart layouts
- PDF/CSV exports
- Suggesting:
- Typography and color usage
- Spacing and safe-zone rules around logos
- Reviewing:
- New UI components for brand consistency
Brand Basics
-
Fonts:
- Headlines: Inter (bold/semibold)
- Subheads & body: Poppins (regular/medium)
-
Colors:
- Light backgrounds: #F2F2F2, #FFFFFF
- Accent / surfaces: #E0D8D1
- Primary text: #292929
-
Logo Safe Zone:
- Maintain at least one logo-height of padding around the full logo.
- For icon-only usage, safe zone = ½ icon size.
Guidelines
- Use Inter for key metrics & section headings; Poppins for tables, annotations, and longer copy.
- Preserve adequate white space and avoid crowding charts or tables.
- Ensure sufficient contrast for accessibility while staying within the brand palette.
- When generating LP-facing text, keep tone:
- Clear
- Professional
- Evidence-based
Invariants
- Never stretch or recolor the logo outside defined palettes.
- Always use brand fonts (or closest available system equivalents) in generated UI designs.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?