'first run' 검색 결과

Run an infrastructure-first security audit of a repository - secrets archaeology, dependency supply chain, CI/CD pipeline, LLM/AI attack surface, agent skill supply chain, OWASP Top 10, STRIDE threat model, and data classification - with a confidence gate and a pre-emit verification gate that suppress speculative findings. Use when asked for a security audit, threat model, pentest-style review, OWASP pass, or a pre-release security check. Not for reviewing a single diff - use requesting-code-review for that.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Systematically find and fix performance problems in applications, frontend and backend, by measuring first. Use this skill whenever the user reports slow endpoints, high latency, poor throughput, memory leaks, large bundles, or slow page loads; wants to profile with cProfile, py-spy, Chrome DevTools, Node --cpu-prof, or perf; run load tests with locust or k6; set performance budgets or SLOs; optimize database queries (EXPLAIN, indexes, N+1); add caching (Redis); improve frontend performance (code splitting, lazy loading, image optimization, memoization, virtualization); or tune the network (CDNs, gzip/br, HTTP/2/3). Also trigger for p50/p95/p99 latency, throughput, error rate, connection pooling, async vs threads, GIL, and memory leak investigations.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when implementing a new function, adding a feature, fixing a bug, refactoring with test coverage, or writing a new test. Enforces strict outside-in red-green-refactor TDD with one-failure-per-turn discipline, predict-the-failure-before-every-run checks, hardcode-first minimum changes, triangulation, and property-based testing for large input spaces. Triggers on explicit TDD requests and on any task phrased as "implement", "add", "write a function", "build a feature", or "fix a bug" in a test-capable codebase. Reports red/green validation evidence.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run one explicit escalation pass using the original glaze prompt words verbatim. Use when prompts say `/tw-glaze`, when the first answer feels merely adequate, or when you want the exact original rhetoric preserved while pushing for a materially stronger direction.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when adding a test to an existing codebase for behavior that is already implemented. Ensures the test is meaningful by mutation-verifying it — breaking the production code to confirm the test fails for the expected reason. Triggers when the user says "add a test for existing behavior", "backfill test coverage", "the test passes on first run", or any scenario where a test is written without a corresponding new production change.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run a second, harder escalation pass using the original glazer prompt words verbatim. Use when prompts say `/tw-glazer`, when a first escalation still feels incremental, or when you want the exact original rhetoric preserved while forcing a sharper replacement rather than more polish.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run a two-agent independent review/redteam followed by peer collaboration to produce a consensus superset of findings and enumerated revision requests. Use when Codex 5.5 and Claude Opus 4.7 should first critique a matter independently, then exchange work, synthesize the best combined analysis, and finish with a single agreed revision list.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Publish a new Canvas Notebook release. Use this skill whenever the user asks to bump a version, prepare release notes, update CHANGELOG.md, create or push a git tag, publish a GitHub Release, deploy, or automate the release workflow. This skill covers the full release sequence for this repository: inspect commits/tags, push completed product-code commits first when authorized, confirm the pushed code has built on GitHub, choose the next calendar version, update package and CLI versions, update the changelog, run the required local build, commit, push the release commit, wait for the remote Build and Push worker on the pushed branch, tag, push the tag, and publish the release.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when designing or implementing empty, first-run, no-result, offline, error, or waiting states in Apple-platform apps — every empty state explains what is missing, why it matters, and what to do next.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user adds a project to the workspace, opens an unfamiliar repo, asks "what is this project", "explain this codebase", or invokes explain-new-project. Explores a newly opened workspace project and writes a plain-language report for a self-taught, non-technical user—quick start (what it is + how to run) first, then optional depth—and always saves PROJECT_GUIDE.md in the project root.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use FIRST when user requests any disease market sizing report (e.g. "做 X 市场调研" / "Run market sizing for X"). Elicits 4-6 startup questions (evidence window, geography, international comparison, report depth, user role) and writes .cache/<slug>/contract.json. ALWAYS invoke before disease-market-sizing-orchestration. Validates against schemas/contract.schema.json.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Audit and optimize a skill system with evidence. Use for skill architecture, token or context waste, role and prompt boundaries, routing hits or misfires, plugin packaging, registry/docs/source drift, duplicate workflows, or deciding whether a reusable change belongs in a skill. Runs deterministic checks first and applies only authorized, minimal fixes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Produces a deep, honest peer-review of how someone uses Claude Code by statistically analyzing their local session data (~/.claude/usage-data/ and ~/.claude/projects/). Trigger whenever the user asks to review, analyze, audit, or critique their own Claude Code usage, workflow, habits, or skill level — including phrases like "analyze my cc usage", "review my cc sessions", "peer review my cc workflow", "deeper than /insights", or any ask for an honest audit of their AI workflow. Also covers portfolio/hiring-manager framings (e.g. "portfolio for Anthropic/OpenAI/xAI"), but ALWAYS ask the user in Step 0 which version to build (self / hr / both) before running — never silently produce an HR report, because that version goes to outsiders and needs explicit privacy setup. The HTML report is laid out ledger-first for SELF (opening band, output/team/leak/trend ledgers, then peer review, 9-dim scoring, try-this-week, case study, claim-indexed evidence). The HR variant is a recruiter version v1: identity card, earned badges (threshold-based, earned-only), allowlist-filtered output ledger, one case study, and a methodology & scope disclosure — no scores, no peer-review memo, no charts.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

What every Ollama timing field means and the arithmetic that turns it into a claim - tokens per second, time-to-first-token, why total_duration is not latency, why a second run is faster, what changes with context length, quantization, GPU offload and parallel requests - plus the reporting rules that make a benchmark a measurement instead of an anecdote.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Project-orientation workflow (/orient): installs predicate's enforcement into a target project, maps its structure and goal, and authors the persistent conditioning layer (AGENTS.md goal-hierarchy) so every subsequent walk is anchored and gated. Trigger when: - Onboarding a new project into predicate for the first time. - Refreshing an existing project's AGENTS.md hierarchy against the current state of the repository (re-run = refresh). - Prompt contains: /orient, orient workflow, onboard project, project orientation, AGENTS.md hierarchy, persistent conditioning layer.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

The crouton-conformance gate — the SECOND acceptance axis of graduation (the first is the experience side-by-side, /graduate stage C1). Checks a graduated app is a REAL crouton app — CLI-scaffolded, real collections, consumes the correct packages without reinventing them — by composing the existing probes (frontend-review, a11y, e2e-smoke, typecheck) plus crouton-structural checks, then renders a required, signed-off checklist on the graduation PR. Use at /graduate stage C2, or when asked "is this app crouton-native", "run the conformance gate", "check graduation conformance".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Cleanly tear down a crouton poc/app — the inverse of /deploy. Removes the code, the Cloudflare Worker + D1 + KV (both env scopes), the app's stray branches, and closes its epic/sub-issues — with a --dry-run first and a typed confirm for anything destructive. Use when asked to "remove an app", "tear down a poc", "delete app X and its resources", or to clean up after an abandoned proof-of-concept. Counterpart to /deploy, /poc-deploy, crouton init.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Before creating a GitHub issue or epic, search for an existing related one and force a reuse / replace / new decision — so the issue-first flow can't silently mint a duplicate. The create-time half of the dedup gate (the pickup-time half is /issue-sanity-check). Use whenever you're about to open an issue/epic, or run /issue-dedup. Backed by a hard PreToolUse hook on issue_write create.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Cucumber BDD integration for AID methodology. Gherkin-first acceptance criteria with executable specifications. Use for writing feature files, step definitions, and running acceptance tests.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Scan code, dependencies, containers, IaC and SBOMs with Snyk via its first-party MCP server: authenticate, trust a folder, run the right scanner, read the findings, fix and re-scan. Includes package-health checks before adding a dependency.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create, verify, transfer, and resume compact project handoff packets for long-running Codex work. Use after a second observed automatic context compaction, immediately after a third compaction, when attention or constraints degrade, a major phase ends, the user asks to move work into a fresh task, work must pause, or an existing handoff needs to be imported. Do not interrupt after the first normal compaction. Always ask before creating a new task, transfer the global roadmap only after explicit consent, preserve the old task title when available, then require the fresh task to ask what work matters most. Preserve objectives, constraints, decisions, evidence, approval boundaries, workspace state, validation, and risks without treating an old summary as current truth.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.