Results for “things”

Design the small details -- triggers, rules, feedback, loops and modes -- that separate good products from great ones. Use when the user mentions "microinteraction", "button feedback", "loading state", "toggle design", "animation detail", "interaction polish", "state transitions", or "input feedback". Also trigger when designing form validation responses, progress indicators, confirmation dialogs, or any UI element where the user expects immediate feedback. Covers trigger design, state rules, feedback mechanisms, and progressive loops. For overall UI polish, see refactoring-ui. For affordance design, see design-everyday-things.

Turn a cold start into a warm one. Build a single orientation document for a project, account, or workspace, what it is, where things live, the decisions made so far, the open items, and the next move, so a new session or a new teammate is productive in minutes instead of days. Trigger on "get me up to speed", "onboard someone to this", "what's the context here", "brief a new session", "orient me on this account", or any cold-start on work already in motion.

Multi-tiered memory management (HOT/WARM/COLD) for context compaction. Invoke ONLY for explicit compaction events: post-`/compact` cleanup, MEMORY.md tier promotion, archive batch, or "trim my context". NOT for general recall (use deep-recall) or routine memory writes (use storage-router). Triggers: "compact memory", "promote to durable", "archive old context", "tier this".

Creates long-form magazine-style articles with hero sections, serif headings, styled quotes, code blocks, and call-to-action cards, suitable for Substack, Medium, or blogs.

Create bucket lists with categorization and planning. TRIGGERS - Use when user needs help with bucket-list related tasks.

Create and update pitch decks, one-pagers, investor memos, accelerator applications, financial models, and fundraising materials that stay internally consistent across multiple assets.

Bags - The Solana launchpad for humans and AI agents. Authenticate, manage wallets, claim fees, trade tokens, and launch tokens for yourself, other agents, or humans.

Strengthen interfaces against edge cases, errors, internationalization issues, and real-world usage scenarios that break idealized designs.

Provides idiomatic React 18/19 patterns for hooks, server/client components, Suspense, error boundaries, forms, data fetching, state management, and accessibility-first composition.

Inventory of the intelli-verse-x product portfolio — what each product is, its repo, primary tech, deployment status, and which other product/service it's coupled to. Use whenever the user mentions a product by name (Quizverse, IntelliverseX, Hyperframes, Brackt, IntelliverseSpace, Intelliverse-X-AI, Intelli-verse-X-SDK, content-factory, etc.) and you need the canonical pointer for what it does + where it lives.

Triggered by "tidy up", "clean up transactions", "categorize uncategorized", "organize my transactions"

Identify opportunities to add moments of joy, personality, and unexpected polish that transform functional interfaces into delightful experiences.

Inventory Items in a Fabric Workspace

Use to clean up sprawling helpdesk tags, categories and custom fields so reporting built on them means something. Trigger for "our tags are a mess", "consolidate our ticket categories", "why don't our tag reports add up", duplicate or near-duplicate tags, tags nobody uses, agents tagging inconsistently, or before building reporting on top of tags.

SKILL — Brand Systems

Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.

Plan team outings with activities and logistics. TRIGGERS - Use when user needs help with team-outing related tasks.

Close the gap between "you corrected me" and "it never happens again." Scan a work session for the corrections you made, the things you approved, and the patterns that held up, then propose specific edits to your skills, playbooks, and docs, high-confidence corrections separated from medium-confidence patterns, with nothing changed until you approve. Trigger on "learn from this session", "what should we update", "turn this into a rule", "close the loop", "improve the playbook", or the end of any session where you corrected or approved the work.

Approach an app, tool, codebase, website, or product as a genuine first-time user with zero insider context — try it out using only the information provided, get confused where a real newcomer would, and surface the "obvious" questions that people who built or use the thing daily can no longer see. Use this whenever the user wants a first-time-user test, a fresh perspective, a naive walkthrough, a cold read of their README/onboarding/docs/UI, or says things like "pretend you've never seen this", "would a new user get this?", "test my app like a beginner", "what would confuse someone new?", or "give me fresh eyes on this". Also use it when someone wants to find gaps in onboarding, docs, or first-run experience — even if they don't say "fresh eyes" explicitly.

Write the context brief a first-time tester gets before testing an app, tool, codebase, or product — it explains WHAT the thing is and why it exists, while deliberately withholding HOW anything works. The companion to the fresh-eyes skill; the brief it produces is the "starting information" handed to a fresh-eyes tester. Use this whenever the user is preparing a fresh-eyes or first-time-user test and needs the setup material, or says things like "describe my app without giving anything away", "write the context card for the tester", "explain what it is but not how to use it", "set up the newcomer test", "what would the tester be told going in?", or wants a spoiler-free description of their product. Also use it when someone asks for the briefing/intro that a new tester, new hire, or evaluator should receive before first contact with the thing being tested.