Apple's approach to interface design and fluid, physical motion, translated for the web. Use when building or reviewing gesture-driven UI, spring animations, drag/swipe/sheet interactions, momentum and interruptible transitions, translucent materials and depth, typography (optical sizing, tracking, leading)…
This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.
Generate flat, minimal light/dark-aware SVG diagrams as standalone HTML files, using a unified educational visual language with 9 semantic color ramps, sentence-case typography, and automatic dark mode. Best suited for educational and non-software visuals — physics setups, chemistry mechanisms, math curves, physical…
Use when the user requests diagrams, flowcharts, architecture diagrams, ER diagrams, UML / sequence / class diagrams, network topology, ML/DL model figures (Transformer/CNN/LSTM), mind maps, or any visualization. Also use proactively when explaining systems with 3+ components, complex data flows, or relationships that…
★not rated 26▲
+2 3d agoASkillSpector: warn120 tokens
originalMIT
Structure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters", "hexagonal architecture", "use case boundary", "onion architecture", "screaming architecture", or…
★not rated 26▲
+2 3d agoASkillSpector: pass122 tokens
originalMIT
Use when architecture work hinges on DDD-style domain modeling: subdomains, bounded contexts, context relationships, aggregate boundaries, and how those decisions shape overview or detailed design artifacts.
★not rated 26▲
+2 3d agoASkillSpector: pass43 tokens
originalMIT
Use when an architect must start at the demand-research stage, turn a business problem into a researchable architecture problem, and preserve the full lifecycle-stage doctrine for what to ask, what to answer, and what the business-research document must contain.
★not rated 26▲
+2 3d agoASkillSpector: pass58 tokens
originalMIT
Use when an architect must decide which architecture lifecycle stage to enter next, route to the correct stage methodology skill, and apply the merged lifecycle backbone as one coherent delivery chain rather than as separate old and new skill systems.
★not rated 26▲
+2 3d agoASkillSpector: pass50 tokens
originalMIT
A method for creating and reviewing deployment or physical architecture diagrams that show where a system runs, its network and deployment boundaries, and assumptions needed for operations.
★not rated 26▲
+2 3d agoASkillSpector: pass62 tokens
originalMIT
Use when an architect must run the deployment-and-operations handoff stage, preserve the full lifecycle-stage doctrine for deploy/ops, and turn completed design into physical topology, rollout, operations, monitoring, emergency, and rehearsal deliverables.
★not rated 26▲
+2 3d agoASkillSpector: pass58 tokens
originalMIT
A method for designing and reviewing a business-solution architecture: a middle-level view that connects confirmed business problems to a solution before technical implementation is designed.
★not rated 26▲
+2 3d agoASkillSpector: pass57 tokens
originalMIT
A method for drawing and reviewing business process flowcharts during solution design. These diagrams show which roles perform which steps and how work is handed from one role to another.
★not rated 26▲
+2 3d agoASkillSpector: pass57 tokens
originalMIT
Use when an architect must run the solution-design stage after demand research, preserve the full lifecycle-stage doctrine for this stage, and turn business research into solution-design outputs such as business flow, domain model, solution architecture, risk controls, and milestone framing.
★not rated 26▲
+2 3d agoASkillSpector: warn60 tokens
originalMIT
A method for creating and reviewing detailed flowcharts and state machines that show how a system handles actions, decisions, and every important branch.
★not rated 26▲
+2 3d agoASkillSpector: pass53 tokens
originalMIT
Use when an architect must run the detailed-design portion of technical design, preserve the full lifecycle-stage doctrine for detailed design, and define the concrete runtime, project, flow, data, interface, non-functional, security, recovery, hardware, and implementation-plan surfaces needed for execution.
★not rated 26▲
+2 3d agoASkillSpector: warn65 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: