Loading...
Loading...
Found 12 Skills
Core philosophy for designing Claude Code skills - when to use skills vs agents, the knowledge test, and what makes skills valuable. Use when deciding component type or evaluating skill quality.
Manage software complexity through deep modules, information hiding, and strategic programming. Use when the user mentions "module design", "API too complex", "shallow class", "complexity budget", or "strategic vs tactical". Covers deep vs shallow modules, red flags for complexity, and comments as design documentation. For code quality, see clean-code. For boundaries, see clean-architecture.
Design thinking principles for distinctive interfaces. Covers aesthetic direction, anti-patterns, and avoiding generic AI-generated aesthetics.
Model software around the business domain using bounded contexts, aggregates, and ubiquitous language. Use when the user mentions "domain modeling", "bounded context", "aggregate root", "ubiquitous language", or "anti-corruption layer". Covers entities vs value objects, domain events, and context mapping strategies. For architecture layers, see clean-architecture. For complexity, see software-design-philosophy.
Apply named refactoring transformations to improve code structure without changing behavior. Use when the user mentions "refactor this", "code smells", "extract method", "replace conditional", or "technical debt". Covers smell-driven refactoring, safe transformation sequences, and testing guards. For code quality foundations, see clean-code. For managing complexity, see software-design-philosophy.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
Visual art and static design creation. Outputs: .png, .pdf documents. Capabilities: poster design, infographics, visual art, design philosophy creation, composition, layout. Actions: create, design, compose, generate posters/art/infographics. Keywords: poster, infographic, visual art, canvas, composition, layout, PDF design, PNG creation, graphic design, visual hierarchy, design philosophy, aesthetic movement, static design, printable, artwork. Use when: creating posters, designing infographics, generating visual art, making static designs, producing printable materials, expressing design philosophies visually.
Design visual layouts and compositions for web and print. Creates balanced designs with typography, color, and spacing principles applied consistently.
Create exquisite visual artworks in .png and .pdf formats using design philosophies. This skill should be used when users request posters, artworks, design pieces, or other static works. Create original visual designs and do not copy existing artists' works to avoid copyright infringement.
Deep analysis of GitHub repositories to understand their core architecture, design philosophy, technical decisions, and implementation patterns. This skill should be used when users provide a GitHub URL and request comprehensive understanding of the repository's structure, purpose, key abstractions, or technical approach.
Creates visual design philosophies and expresses them as static art in PNG and PDF formats using composition, color theory, typography, and graphic design principles. Use when asked to "create a poster", "design artwork", "make a visual design", "create static art", or "design a graphic piece". Develops aesthetic movements through form, space, color, and minimal text as visual accents. Works with PDF and PNG output files plus markdown design manifestos. Produces original visual designs using design philosophy methodology rather than copying existing artists.