261 assets · page 5 of 11
This skill should be used when users drop off mid-task, motivation fades, or experiences feel flat. Applies Peak-End Rule, Goal-Gradient Effect, and Zeigarnik Effect.
Design and implement memory architectures for agent systems. Use when building agents that need to persist state across sessions, maintain entity consistency, or reason over structured knowledge.
Design multi-agent architectures for complex tasks. Use when single-agent context limits are exceeded, when tasks decompose naturally into subtasks, or when specializing agents improves quality.
Use this skill when writing commands, hooks, skills for Agent, or prompts for sub agents or any other LLM interaction, including optimizing prompts, improving LLM outputs, or designing production prompt templates.
Generate minimal HTML pages to review Claude Code output in a browser. Use when terminal output is hard to read, when reviewing lists/tables/drafts, or when user says "show me", "make this reviewable", "quick view", or "open as webpage". Produces unstyled semantic HTML only.
This skill should be used when the user is stuck, obvious solutions aren't working, constraints feel impossible, or they keep circling back to bad options. Use when designs keep getting rejected or the user is solving symptoms instead of root causes.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Use when building anything non-trivial. Enforces a spec → plan → execute → verify loop that prevents "looks right" failures. Creates spec.md, todo.md, and decisions.md before writing code.
Structure an app around objects when starting a complex app from scratch, existing navigation feels messy, users can't find things, or the IA is getting worse as features are added. Use Object-Oriented UX to design around nouns, not verbs.
Design tools that agents can use effectively, including when to reduce tool complexity. Use when creating, optimizing, or reducing agent tool sets.
Analyze and improve UI density using Matt Ström's 4-dimensional framework. Use when interfaces feel too sparse, too cluttered, or when users complain about efficiency.
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
Use when an agent needs ALMA scorecard data - regions, scorecards, indicators, period-to-date maps, data-point time series and region geo for a given ALMA tenant. Wraps ALMA's embedded, read-only hosted MCP endpoint (per-tenant `/mcp` on the tenant API host), so every tool runs as the connected Personal Access Token's role + region scope. Reach for this over raw REST/OpenAPI when the task spans several ALMA reads or you want typed, permission-scoped tools (e.g. joining indicator time series against weather).
The collection's application-design rulebook, installed as one asset: invariant rules, tunable heuristics, an adoptable defaults bundle and the floorplan catalogue that an app's APP-DESIGN.md adopts and records against. Not invocable.
Slow visual critic for app-explore: reviews the given screens' screenshots and data against Nielsen's 10 heuristics and OOUX consistency, guided by example critiques when the brief has them, and writes critique/<batch>.json findings with marks, boxes, severity and confidence.
Persona walker for app-explore: acts as one persona pursuing one task in its own browser tab, thinks aloud per step, respects read-only mode, and writes walks/<task>.json with steps, success, clicks and a post-task survey.
Explore a running web app like a user and report its perceived objects, tasks, navigation and visual clarity with an annotated screenshot gallery. Use for 'explore my app', 'how clear is my app', 'UX audit of <url>', or re-running against a previous app-explore report.
Use when the project needs a schema before or while features are specified — derives entities, relationships and enums from whatever exists (glossary, journeys, features, findings, the brief), cites a glossary term for every entity, compares the consequences of the expensive modelling choices with the user, and writes the stack-neutral model with its seed scenarios. Triggers on 'data model', 'design the schema', 'what entities do we need', 'seed data'.
Use when the stack is chosen and the features need more than the stack ships with — records the custom modules, protocols and external integrations this project adds, and stops there. Triggers on 'architecture', 'system design', 'do we need a websocket', 'which modules', 'how does this talk to Stripe'.
Use when a project has no technology decided — scans the stack templates on disk, asks what the project actually constrains, and records the winner as the one id every later skill resolves. Triggers on 'tech stack', 'what should we build this with', 'pick a framework', 'which template'.
[skaile-development] Monorepo-aware code quality audit for the skaile-dev codebase. Verifies build (lint + typecheck + build) and tests pass, then dispatches three parallel sub-agents for logic, security, and UI/UX findings. Three scopes: diff (staged or last-commit), package (one package deep), full (whole monorepo). Produces _devlog/reports/audit-<date>.json. Use before opening a PR or cutting a release.
Autonomous multi-agent skill for writing professional medical textbooks in child and adolescent psychiatry. Simulates a 5-agent team (Architect, Researcher, Pedagogue, Writer, Critic) to produce evidence-based, guideline-grounded content using a layered file architecture. Concept, research, scaffolds, and prose are stored in separate files. Triggers: "Write a book about...", "Start a book...", "/start_book", "/plan_chapter", "/write_chapter".
Use when implementation work needs somewhere to live or somewhere to go — opens the build branch and optional worktree before the first slice, and merges, PRs, keeps or discards it after the last. Triggers on 'start implementing', 'set up the branch', 'finish the branch', 'merge the work'.