Loading...
Loading...
Found 1,744 Skills
Rebuild an existing site's pages with byte-faithful content on a separately-defined donor design system — another live site, or local static HTML prototypes (Figma donors are contract-defined, not yet implemented). Content fidelity is gated byte-level (text, ordered images, SEO metadata); design application is flexible (content re-laid-out onto donor modules). Use when the user says "reskin my site with this design", "apply this design system to my content", "restyle my site to look like <other site>", "new design, same content", "rebrand my site using these prototypes", or names a content site plus a design donor. NOT for redesigning from intent (that's the stardust core extract/direct/prototype chain) and NOT for keeping the current design while migrating (that's the replica flow).
Create a COMPLETE, render-safe brand kit for ANY brand under brand/<id>/ — design.md + the editorial engine (editorial/) + an engine-agnostic voice lock + outlined logos + palette-driven static & dynamic backgrounds + device mockups + stickers + a brand board & sheet + a brand.json manifest. The kit is consumed by /use-brand, which turns it into any deliverable — website, slide deck, PDF, social/OG cards, marketing copy, dev tokens, or a video (handed to /make-video). Two modes - GENERATE from scratch via an interactive discovery flow + a multi-direction inspiration board the user picks in the browser, or IMPORT an existing brand by crawling its portal. Self-contained - every generator reads bundled templates in $SKILL_DIR/assets/, never a reference kit. Trigger - /make-brand.
Embed a Factorial Code process's input-parameter form on a webpage — the three embed methods (data attributes, Fcode.initForm, the FcodeForm React component), version pinning to the stable alias, access restriction (authMode), driving behavior from the process return value, styling and themes (including the f0 theme inside Factorial), multi-step flows, pre-filling current values, and file uploads. Use when embedding, configuring, styling, restricting, version-pinning, pre-filling, or wiring up a Factorial Code (fcode) form.
Use when writing or reviewing Jetpack Compose state ownership, remember state, state hoisting, screen state holders, LaunchedEffect, DisposableEffect, SideEffect, Flow collection, navigation, snackbar, analytics, or focus requests.
Open a running local app in Design overview mode as URL-backed iframe screens for visual editing, flow review, duplication, and route-state exploration. Use when the user asks to inspect, compare, or edit a real local app visually in Design.
Control the brain's information processing flow through the three stages of metacognition. Use this method when you "know what to do but can't follow through", can't think rationally after being emotionally hijacked, or need to systematically improve the quality of your brain's information processing. The three stages: Control Input (attention acts as a gatekeeper for information entry) → Control Brain (discard/store/process information) → Control Output (execute thinking results with high quality). Not applicable to emergency scenarios requiring rapid instinctive responses. Key trigger signals: "Know but can't follow through", "I'm emotional again", "My mind is messy", "Learned but can't apply it".
Correct, create, or remove written material so a later reader can rely on it: documentation that no longer matches the system, a fact about to be written down a second time, prose restating what a config file or command already prints, a records folder that has drifted, or a decision worth recording so it stops being re-argued. Prose no human has read counts as a hypothesis, not a source. Use when the user says "the docs are out of date", "readme still says the old flow", "where does this go", "write this down", or "should this be an ADR". Not for judging docs inside a change under review, explaining an existing document, or looking up a third party documentation.
Find refurbished/recertified used memory (RAM) on Newegg — this maps to Newegg's official Recertified/Refurbished Memory Store, covering Desktop/Laptop/Server memory, with brand, capacity, DDR generation, price, and model number info. Newegg has no C2C private used-goods marketplace; this skill returns officially refurbished / trade-in refurbished memory only. Supports semantic price intents like "cheaper option" or "budget-friendly" via a two-step semantic-search + price-enrichment flow. Triggers: "used memory", "used RAM", "refurbished memory newegg", "recertified memory", "cheap refurbished RAM", "budget refurbished memory", 二手内存条, 二手内存, 翻新内存条, Newegg二手RAM, 便宜的二手内存, 预算内的翻新内存.
generate, refine, validate, and render diagrams from natural language, notes, code snippets, schemas, tables, or existing diagram source. use for flowcharts, swimlanes, sequence diagrams, state diagrams, er diagrams, class diagrams, architecture/c4-style diagrams, dependency graphs, gantt charts, mind maps, user journeys, sankey-style flows, org charts, network graphs, and other visual models. supports mermaid by default, graphviz dot for complex graph layout, plantuml for uml-heavy engineering diagrams, and svg output when direct markup is more reliable.
Use the codeintel command-line tool: intelligent indexing and field trace query for Go codebases. Features include building indexes (init), querying symbol/field read-write summaries (query fields), field tracing (trace-backward/forward), full-chain data value tracing (value-trace), call relationship analysis (callers/callees/impact), export (export), and Web service (serve). This skill is used when users request to analyze field data flows in Go codebases, trace field users/producers, check function field read-write operations, or query call relationships.
Use this skill when an agent needs to write reusable code, store it under the configured Hermes Code folder, run it directly through local code execution, or host it behind a Make-managed E2B Code Shell scenario. Use for tool-building, generated business automation scripts, and nested flows where hosted code calls Make API shell scenarios for SaaS access without receiving raw OAuth, Make, or E2B secrets.
Stand up (or extend) an operator-only in-app scratchpad / internal test-bed — a single gated internal page that reuses the project's real components and library functions so you can judge work-in-progress by eye: eyeball generated visuals (OG/social cards, emails, avatars, empty states), compare variants side by side or with live sliders, check config/env readiness, and exercise real side-effecting flows with fake data — without shipping any of it to users or clicking through the whole product. Boards and config panels get a "Copy as JSON" button so a tuned-by-eye result round-trips straight back into the code or to an agent to apply. Bootstraps into the user's existing stack: detects the framework, auth, and env conventions, writes a fail-closed access gate first, then a route with a section switcher seeded from their own code. Use when a user says "spin up a scratchpad", "internal test bed / dev playground / sandbox page", "an operator/admin preview page", "a page to eyeball my work", "preview my OG cards / emails / component variants", "add a test page for these components", or "an internal page to exercise a flow with fake data". NOT for public/user-facing features, NOT a replacement for tests (pass/fail machine-checkable → write a test), NOT Storybook (this lives inside the real app), and NOT a place to do load-bearing production operations.