1.4천건 · 관련도순
Use when working through architectural flaws documented in a .reviews/architecture/ report — selecting which flaws to fix, resuming a partial fix session across multiple sittings, or applying structural changes that need to be tracked back to a report. Not for producing that report — run the agentic-architecture skill first if there isn't one.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run an authorized, local-first application security assessment on the current project using this agent's own reasoning. Use when the user invokes Myrqen, asks to security-test or pentest the app they are building, asks whether their app has real vulnerabilities before shipping, wants a Myrqen finding validated, or wants a Myrqen remediation applied and retested.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Walk through a product's key flows with Firecrawl browser and produce a structured UX/product walkthrough. Use for signup, onboarding, pricing, docs, dashboard, product demo prep, UX teardown, and first-run experience analysis.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build and verify a HyperGrok trading desk from the pinned public release. Use for first-run setup, repair, or a readiness check. Starts with a live zero-key Opening Bell, installs the seven role profiles and seventeen shared skills, prepares the Trading Floor, and returns an evidence receipt. Read-only by default; never requests a wallet or places an order.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Automatically fix skill problems (safe preview first). Also use with --prune to find and remove broken symlinks, empty directories, and orphaned skills. Trigger with '/janitor-fix'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use after the first trace of a diff and before the verdict - pick the attack-class skills each touched surface needs, give every risky surface a disposition, ask the coverage-critic questions (parallel paths, lifecycle modes, handoffs, second-order use), search variants of every HIGH/CRITICAL root cause, and run the literal obvious-things sweep
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when writing or changing any React component - React Testing Library tests are behavior-focused (byRole first), use user-event, assert on accessible output, one behavior per test, and run in npm test
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build and debug SceneKit scenes where one 3D object (a product, badge, coin, wheel) performs on a transparent stage inside a SwiftUI app - studio lighting, real shadows, baked keyframe choreography, hand-rolled physics, gestures and haptics, multi-scene sequencing. Use when working with SCNView or SceneView in SwiftUI, UIViewRepresentable 3D scenes, product or hero-object animation, roll or spin entrances, a first-frame hitch when a scene appears, shadows missing or wrong, metal rendering black, choreographed 3D motion that must stay interruptible, a continuous vapor stream (vent air, steam, mist) drawn as a shader-driven sheet, a liquid-metal or jelly blob (noise-deformed surface with mirror reflections and tap ripples), chrome or gold that looks cartoon-flat instead of real, HDRI image-based lighting, free trackball rotation of an actor, deterministic screenshot testing of shader-driven scenes, cutting an actor in two with a finger swipe (runtime mesh slicing with sealed cross-sections and a falling piece), a die-struck relief object (badge, coin, medallion) built from a heightfield with multiple finishes on one mesh, an actor crumbling into debris that falls and rests on the floor, reproducing a real object's motion from photos or video, or keyframed motion that stutters at its own keyframes. Not for RealityKit, ARKit, visionOS, or full game worlds.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run structured brainstorming sessions (divergent/convergent), improve prompts with 7-dimension framework, and apply decision frameworks (RICE, weighted scoring, first principles, pre-mortem).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Welcome and set up a new Claude for Financial Advisors user. Gets to know the advisor's RIA, learns their day-to-day pain points and tech stack, walks them through connecting their tools, explains the plugin and how skills work, runs a live pre-meeting demo, shows them how to customize skills, and closes with a personalized recommendation for which skill to try next. Use when the advisor is getting started or says any of: "onboarding," "/onboarding," "get started," "help me get started," "set up claude for financial advisors," "claude for financial advisors setup," "what can this plugin do," "I'm new to this," "show me around," or is in their first session with the plugin.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
S6 of see-it-ship-it: put it at a public URL. Secret scan first; static builds go to GitHub Pages at no cost (sign-up guide, device-code login, one question: it will be public); a server only when a backend is needed, cost asked once; then open the URL, rerun the acceptance on the live page, bind a domain if they want one.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reviews a change before it is merged, from little or no input. With nothing typed it reviews the branch you are on, uncommitted work included, against its base, its PR and its ticket, so a developer can check their own work before asking for review. With PR links, repo#N or a branch it reviews someone else's change the same way, several repos at once. It judges the failed CI checks and every Bugbot and reviewer comment, gets a fresh breaker review, traces every other piece of code that uses what changed, proves each finding or marks it unproven, says what the merge needs (a build, env vars, migrations, deploy order) and how to check the deploy, never posts to GitHub, and offers fixes only after the report. Runs only when the user types it.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Sets up, checks or changes the optional Jev judge, the TypeSafe decision model that ship-check asks about review findings (is this real harm, is a small one worth fixing now, what proof does a small fix need). Shows whether it is on for each repo, which key it uses, switches it on or off, and sends one test request. Runs only when the user types it.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run before writing or changing code for any feature, bug fix or refactor that touches data, jobs, money, outside services or user-facing behaviour. Finds where the change will break before it is built, by walking ten named failure classes (twice, halfway, outside call, failure-is-not-empty, neighbors, endings, money, hostile user, words, scale and time) against the code, and writes the answers into the plan. Use when planning a change, when asked to "think it through", "cover the gaps", "make sure it's bug free", or before any edit to payment, publishing, deletion, auth or background-job code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Lifts the task's scope for one task. The session, its reviews and fix-the-class then look across the whole codebase and every repo that shares its code, data or vendors, and every problem found anywhere is handled by the usual rules. Runs only when the user types it.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Rewrites the prompt typed after the command before any work starts, then works from the rewrite. Splits a mixed-up message into a numbered list of asks, turns words like "be 100% sure", "cover all cases" or "don't break anything" into the checks they stand for, keeps every name, path, number and quote exactly, and stops to ask only where it would have to guess. Runs only when the user types it.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when first setting up lark-cli, running auth login, switching user/bot identity (--as), handling permission denied or scope errors, needing to update lark-cli, or seeing _notice in JSON output.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Processes code review feedback by classifying each finding, reproducing or validating it against the real contract, applying the smallest in-scope fix, and re-running focused proof. Use after comments arrive on a diff, pull request, design, or implementation. Not for requesting a first review or debugging an unrelated failure.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Read this skill before the first step of any request to do something in an app on the person's own computer (Notes, Finder, System Settings, any desktop app), to look at their screen, or for "computer use". Computer use (desktop control) lets Claude take screenshots of the person's desktop and control it with clicks, typing and scrolling through the Claude desktop app; its tools are named mcp__computer-use__* when the session runs in the desktop app and mcp__remote-devices__computer_* when a cloud session is linked to the person's computer; before a conversation is linked there may be no such tools, only an enable__mcp__remote-devices__Claude_Browser tool, which links it. It covers getting linked, picking the right tool, the access flow, and what to do when computer use is off or out of reach. It is not for websites, which go through Claude in Chrome or the built-in browser and their own skills.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Read this skill before the first step that uses the built-in browser, the browser pane inside the Claude desktop app (also called the in-app browser, the browser pane, Claude's browser, or "your own browser"), whose tools are named mcp__Claude_Browser__* when the session runs in the desktop app and mcp__remote-devices__Claude_Browser__* when a cloud session is linked to the person's computer; before those tools are turned on there may be a single enable__mcp__remote-devices__Claude_Browser tool instead. It covers the pane's persistent sign-ins, tabs and preview_start, reading pages as text, site approvals, what the pane cannot open, and what to do when it cannot be reached. It is not for Claude in Chrome (mcp__claude-in-chrome__* tools), which has its own skill, and it does not decide which browser to use.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user wants to turn a static scene, character images, aerial map, drawn path, or route-control image into an immersive first-person FPV AI video prompt, especially Seedance/Kling/Runway/Veo style one-shot videos with numbered stop markers, red-line path control, world-map flythroughs, camera route planning, variable character counts, non-human POVs such as drones, pets, robot vacuums, character references, timed interactions, dialogue, spatial audio, and negative constraints.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
CLI-first serial port debugging and macro automation with serial-mcp-server for Codex and Claude Code. Use when working with UART or USB-serial devices, listing serial ports, probing STM32/Arduino/ESP32 boards, writing or reading serial data, running JSON serial macros, controlling RTS/DTR, or using serial-mcp-server through MCP tools.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Perform a read-only, evidence-first intake of an existing mini-program repository before planning or modifying code. Use when users ask to take over, understand, audit, resume, scope, or continue a WeChat or other mini-program project; when project facts may conflict with historical documents; or when an agent needs the framework, rules, Git state, build path, risks, unknowns, protected behavior, and change boundary. Produces a project fact map and handoff without changing code, installing dependencies, building artifacts, or claiming runtime, device, cloud, upload, acceptance, or release status.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Test a product concept with Amazon's Working Backwards method: write the press release for the finished product first, then answer hard customer and stakeholder questions, ending in a complete PRFAQ document. Use when the user requests to 'create a PRFAQ', 'work backwards', or 'run the PRFAQ challenge'
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.