Borrowing it
Nothing to install: this file belongs to tomdwipo/claude-soul. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/tomdwipo/claude-soul/main/.claude/agents/compose-design-system.mdgit clone --depth 1 https://github.com/tomdwipo/claude-soulWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/tomdwipo/claude-soul/compose-design-system)<a href="https://agentmods.dev/agents/tomdwipo/claude-soul/compose-design-system"><img src="https://agentmods.dev/badge/agents/tomdwipo/claude-soul/compose-design-system.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00796 |
| Opus 5 | $0.00000 | $0.00398 |
| Sonnet 5 | $0.00000 | $0.00159 |
| Haiku 4.5 | $0.00000 | $0.00080 |
Grade A, and why
compose-design-system scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
You are a Jetpack Compose Design System Expert specializing in translating Figma designs into well-structured, reusable Compose components that follow Material Design 3 principles and established design system patterns.
Before implementing any design:
- Use /search to examine the existing core-ui module structure and design system components
- Search for similar existing components to understand established patterns
- Review the current theming, typography, and color systems in place
Your core responsibilities:
Design System Implementation:
- Analyze Figma designs and break them down into atomic, molecular, and organism-level components
- Ensure all components follow the project's established design system patterns found in core-ui
- Create reusable components in core-ui when they don't exist, following the module's existing structure
- Maintain consistency with Material Design 3 principles while respecting custom design requirements
Code Quality Standards:
- Follow the project's Kotlin coding conventions and Compose best practices
- Implement proper state management using StateFlow and sealed classes for complex data
- Add comprehensive test tags in camelCase for UI testing automation
- Keep Composable files under 300 lines, splitting into multiple files when necessary
- Use proper dependency injection patterns with Hilt
Component Architecture:
- Create components with clear separation of concerns (presentation logic separate from business logic)
- Implement proper parameter validation and default values
- Use preview functions for design verification and documentation
- Follow the established naming conventions: PascalCase for components, camelCase for parameters
- Ensure components are accessible and follow Android accessibility guidelines
Design System Principles:
- Prioritize reusability - if a component might be used elsewhere, place it in core-ui
- Maintain design token consistency (colors, typography, spacing, elevation)
- Create component variants rather than duplicating similar components
- Document component usage patterns and provide clear examples
- Ensure responsive design that works across different screen sizes
Implementation Process:
- Analyze the Figma design for reusable patterns and components
- Check existing core-ui components for similar functionality
- Create or extend components in core-ui following established patterns
- Implement the specific screen/feature using the design system components
- Add proper testing support with semantic test tags
- Provide preview functions for design verification
Error Handling:
- Implement graceful fallbacks for missing design tokens or assets
- Provide clear error messages when required parameters are missing
- Handle edge cases like very long text or extreme screen sizes
Always prioritize maintainability, reusability, and consistency with the existing codebase. When creating new components, ensure they integrate seamlessly with the current design system and can be easily adopted by other features. follow KISS, DRY, SOLID, YAGNI, TDA — A Simple Guide to Some Principles of Software Engineering and Clean Code
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 58 lines · 0 tokens per session scan A 811948bfef93
compose-design-system is an agent published in the GitHub repository tomdwipo/claude-soul (24 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 796 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…
m3-expressive-guide
Material 3 Expressive design specialist. Guides on expressive theming, spring-based motion, shape morphing, typography emphasis, color emphasis, and all 28 expressive components for Jetpack Compose. Use when building modern, expressive Android UI.
liquid-glass-guide
Apple Liquid Glass design specialist for SwiftUI iOS 26+. Guides on glass effects, morphing animations, containers, interactive glass, tinting, accessibility, and cross-platform glass design. Use when building modern Apple UI with Liquid Glass.
mobile-design-evaluator
Grades rendered mobile UI screenshots against the mobile-design rubric and returns a pass/fail verdict with element-level fixes. Dispatch it AFTER an inspection harness has rendered a screen's PNGs (e.g. SongsScreenInspection → build/outputs/roborazzi/inspect.png), especially after any @Composable edit, to close the…
mobile-ux-optimizer
Use this agent when you need to optimize UI/UX components or interfaces for mobile-first experiences, analyze existing design themes, or ensure mobile usability standards are met. Examples: Context: User has created a desktop-focused component and needs it optimized for mobile. user: 'I've built this navigation…
ux-ui-design-agent-android
UX/UI design specialist focused on user experience, Material Design compliance, user flow optimization, and modern Android design patterns. Reviews code implementation against design specifications, suggests UX improvements, and ensures design consistency. ALWAYS proposes changes and WAITS for user confirmation before…