'hard rules' 검색 결과

Turn a successful workflow from the current session into a reusable OMC skill draft. Capture inputs, ordered steps, decision rules, pitfalls, and verification evidence, then choose an appropriate storage location.

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

• Preserving a hard-won debugging workflow
• Turning project-specific procedures into skill drafts
• Deciding whether a workflow belongs in a skill or documentation

Set up Cisco Duo multi-factor authentication for VPN, RDP, SSH, and web applications. Configure access rules based on users and device health, introduce security keys, and establish authentication monitoring and emergency access procedures.

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

• Adding Duo authentication to VPN and remote server access
• Strengthening authentication for privileged accounts
• Restricting access based on device health

Recommend where new gbrain pages belong using the active schema pack, a configuration defining page types and storage paths. It also checks existing pages for missing or undeclared types and highlights cases requiring a classification decision.

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

• Choose a storage path before creating a brain page
• Check filing rules before a bulk import
• Apply classification settings for a specific source

Edit videos through conversation, from transcription and take selection to cuts, color adjustments, animated overlays, and subtitles. Confirm an editing plan, review a checked preview, and refine the result before the final render.

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

• Select the best takes for a presentation video
• Trim tutorials and add subtitles
• Shape interviews or travel footage

Explicitly save debugging discoveries, project conventions, and working preferences to Claude's persistent project memory. The skill checks for duplicate notes, keeps entries concise, and suggests moving enforceable rules into CLAUDE.md when appropriate.

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

• Preserving hard-won debugging discoveries
• Recording undocumented project conventions
• Remembering tool-specific commands and pitfalls

Build or update Figma screens from code or descriptions using an existing design system, a shared set of components and visual rules. Assemble sections with reusable components, colors, spacing, and styles, then check their appearance.

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

• Recreate an application page in Figma
• Build a landing page with shared components
• Update a Figma screen to match code

Run repeated reviews of research work, implement fixes, and request another assessment for up to four rounds by default. The workflow records progress and stops when both the review score and verdict meet its acceptance rules.

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

• Revising research work through repeated reviews
• Keeping a record of review findings and fixes
• Resuming an interrupted review process

Create a DESIGN.md guide for generating screens in Google Stitch. Define colors, typography, asymmetric layouts, component states, and motion with precise values and explicit restrictions, giving the agent consistent instructions for a specific visual style.

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

• Set shared design rules for Google Stitch screens
• Define asymmetric page layouts
• Document typography, colors, and interaction behavior

Launch distributed Megatron-LM training on a SLURM cluster with guidance on job scripts, environment variables, GPU settings, and containers. Monitor jobs and investigate failures across worker processes to identify the initial cause.

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

• Write an sbatch script for distributed training
• Configure training across multiple GPU nodes
• Check CUDA settings for the parallelism mode

Remote control of DOCA Flow over gRPC with the shipped `doca_flow_grpc` server: program Flow pipes and entries from Python, Go, Rust or Java, or from another host, instead of linking `libdoca_flow.so`. PLAINTEXT-ONLY: the server uses `grpc::InsecureServerCredentials()` with NO TLS / mTLS / token-auth knob; transport security must come from external infrastructure (e.g. an mTLS proxy / sidecar) on a trusted segment. Trigger even without "gRPC": "program Flow rules from Python on another host", "remotely configure pipes on the BlueField", "client times out connecting to the Flow server", "where is the .proto for Flow", "UNAUTHENTICATED / FAILED_PRECONDITION on a Flow RPC". Covers bringing up, configuring, hardening and debugging the server. Route elsewhere for the underlying doca-flow C API, generic gRPC tooling (protoc, language bindings), or DOCA install / BFB bring-up.

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

Guided journey from a working-but-untested vibe-coded prototype to a production-ready product with tests, clean structure, a business-rules boundary, and resilience at scale. Orchestrates nine skills phase by phase - working-with-legacy-code, clean-code, refactoring-patterns, software-design-philosophy, clean-architecture, pragmatic-programmer, release-it, system-design, ddia-systems - asking the user questions at every decision point and recording results in the project docs/ folder (TESTING.md, TECH-DEBT.md, IMPROVE-CODE-QUALITY-PLAN.md) so the journey resumes across sessions. Use when the user wants to harden an AI-generated prototype, add tests before refactoring, make code safe to change, or says 'this works on my machine but I am scared to touch it'. For an aged codebase, remove-technical-debt; for greenfield structure, design-code-architecture; for a product and UX pass, improve-app; to optimize speed and structure, architecture-optimization. For one framework in isolation, invoke that skill directly.

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

Prevents, detects, and remediates files that should never be committed — secrets (.env, API tokens, hardcoded credentials) and dev artifacts (build output, scratch databases, editor/OS files). Covers .gitignore (and why it does not untrack), git rm --cached, auditing tracked files, history scrubbing, and credential rotation. Use when a repo has committed secrets or junk, when setting up a new repo's ignore rules, or when reviewing what a repo actually tracks.

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

SCIP optimization with PySCIPOpt. Use when facing an optimization problem with an objective, hard constraints, soft penalties, integer decisions, routing, assignment, scheduling, allocation, packing, capacity, inventory, or service-level rules. Prefer modeling and solving the problem with PySCIPOpt when it is available.

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

Screenplay format, page craft, the writing process and adaptation (剧本格式/写作流程/改编) — merged from Wendy Henson (spec format rules), Richard Walter (page craft, revision), Neill Hicks (selling vs shooting script, draft chain), Syd Field (master shot, card method, adaptation as original work), Robert McKee (step outline → treatment → screenplay), Julian Hoxter (format elements, adaptation four questions), Diamond & Weissman (one-page nine-step) and Eric Bork — plus an exact typographic grid, element conventions (V.O./O.S., MORE/CONT'D, dual dialogue), a machine-writable output contract (Fountain, with forced markers for Chinese), and Asian industry formats (Chinese 场号制 影视剧本格式, Japanese 柱・ト書き・セリフ / 決定稿). Use when formatting a spec script, choosing the output file format, deciding what goes in action lines, planning drafts and outlines, cutting pages, adapting a novel, play or true story, writing a Chinese TV/film or Japanese-style script page, or preparing a submission-ready draft.

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

Half-hour television comedy craft (半小时情景喜剧/笑点力学/困境机器/多机位单机位格式) — merged from Evan S. Smith's Writing Television Sitcoms (premise-driven comedy in three levels, nine predicaments, six character mixes, setup/punchline mechanics, toppers, running gags, ten comedic nuances, format rules), Neil Landau's sitcom seven-step formula and comedy-room models, Richard Blum's act-length and set-count parameters, Phoebe Waller-Bridge's Fleabag scripts (direct address as a season-long device, six-episode skeleton), Pamela Douglas on dramedy, Kam Miller on complementary comic traits, and Jesse Armstrong on jokes carrying tragedy. Use when writing or fixing a sitcom episode or spec, raising joke density per page, designing a comic predicament that generates stories, choosing between multi-camera and single-camera format and page counts, structuring cold open/acts/tag, writing a half-hour pilot, running a comedy punch-up, or making a drama funny without shifting genre.

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

Edit any video by conversation. Transcribe, cut, color grade, generate overlay animations, burn subtitles — for talking heads, montages, tutorials, travel, interviews. No presets, no menus. Ask questions, confirm the plan, execute, iterate, persist. Production-correctness rules are hard; everything else is artistic freedom.

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

Score whether a news event is worth newsjacking, or whether a user's pitch idea is actually newsworthy to journalists. Uses calibrated anchors, hard anti-inflation rules, standing checks, timing windows, and brand-safety kill switches.

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

Analyze KiCad projects and PDF schematics: schematics, PCB layouts, Gerbers, footprints, symbols, netlists, and design rules. Reviews designs for bugs, traces nets, cross-references schematic to PCB, extracts BOM data, checks DRC/ERC, DFM, power trees, and regulator circuits. Every finding carries a confidence label and evidence source with trust_summary rollup. Analyzes PDF schematics from dev boards, reference designs, eval kits, and datasheets. Supports KiCad 5–10. Use whenever the user mentions .kicad_sch, .kicad_pcb, .kicad_pro, PCB design review, schematic analysis, PDF schematics, reference designs, Gerber files, DRC/ERC, netlist issues, BOM extraction, signal tracing, power budget, DFM, or wants to understand, debug, compare, or review any hardware design. Also for "check my board", "review before fab", "what's wrong with my schematic", "is this ready to order", "check my power supply", "verify this circuit", OSHWA certification readiness, or any electronics/PCB design question.

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

Use when starting ANY conversation involving Bethesda Game Studio modding, MO2, xEdit, or modpack curation. Bootstrap that loads the toolkit overview, lists available task skills, and enforces the hard rules of this plugin. Auto-injected by the OpenCode plugin's chat.messages.transform hook and by the hooks/ session-start chain in Claude Code and Codex.

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

Use for AI-assisted Unity work that needs live repo discovery, project-derived routing, runtime-owner proof, runtime-visible output hard stops, runtime numeric proof for repeated visible-output failures, state-step guards, multi-agent scope ownership, modular C#/asmdef safety, UI/scene/visual asset gates, data-first content changes, validation, cleanup proof, or durable workflow rules. Best when agents must prove the actual folder/module/scene/prefab/runtime owner before editing, especially runtime UI, generated assets, code graphs, tutorial/state flows, guided selection/action flows, overlay/dim source-bound mistakes, coordinate conversions, focus/highlight/marker/HUD alignment, predictive lead aiming, ballistic trajectories, spatial IoU verification, or repeated "fix still not visible" failures.

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

Analyze KiCad projects and PDF schematics: schematics, PCB layouts, Gerbers, footprints, symbols, netlists, and design rules. Reviews designs for bugs, traces nets, cross-references schematic to PCB, extracts BOM data, checks DRC/ERC, DFM, power trees, and regulator circuits. Every finding carries a confidence label and evidence source with trust_summary rollup. Analyzes PDF schematics from dev boards, reference designs, eval kits, and datasheets. Supports KiCad 5–10. Use whenever the user mentions .kicad_sch, .kicad_pcb, .kicad_pro, PCB design review, schematic analysis, PDF schematics, reference designs, Gerber files, DRC/ERC, netlist issues, BOM extraction, signal tracing, power budget, DFM, or wants to understand, debug, compare, or review any hardware design. Also for "check my board", "review before fab", "what's wrong with my schematic", "is this ready to order", "check my power supply", "verify this circuit", OSHWA certification readiness, or any electronics/PCB design question.

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

Write architecture fitness functions — deterministic tests that enforce a project's hard rules (module boundaries, offline guarantees, content contracts) from inside its own test target. Use when a constraint lives only in prose (CLAUDE.md, code review) and should become un-arguable.

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

Configure host-based firewalls (iptables, nftables, UFW) and cloud security groups (AWS, GCP, Azure) with practical rules for common scenarios like web servers, databases, and bastion hosts. Use when exposing services, hardening servers, or implementing network segmentation with defense-in-depth strategies.

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

Use when you need to design, review, or improve security in Quarkus applications — including Quarkus Security with JWT/OIDC, basic auth, @RolesAllowed / @Authenticated / @PermitAll, SecurityIdentity, permission checks, path-based authorization in configuration, exception mapping for auth failures, and sensitive-data-safe logging. This should trigger for requests such as Add Quarkus security support; Review Quarkus security configuration; Improve API authorization in Quarkus; Add JWT/OIDC security in Quarkus; Harden Quarkus authorization rules. Part of Plinth Toolkit

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