'concise' 검색 결과

Produces a concise, structured analysis report of a codebase: dependencies, workflow, and context.

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

Follow-up review to verify corrections on a MR. Sequential execution to avoid memory spikes. Checks blocking issues, detects new problems, and posts a concise report on GitLab.

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

Angular forms: Reactive Forms (preferred — typed FormGroup/FormControl since Angular 14, FormBuilder, custom + async validators, FormArray, multi-step) and Template-driven (`[(ngModel)]` + FormsModule). Validation strategies, server error mapping, accessibility. Use this skill to: - Build Reactive Forms with typed FormGroup/FormControl. - Use FormBuilder для concise syntax. - Implement custom synchronous and async validators. - Wire FormArray for dynamic field lists. - Map server errors back to form fields. - Pick Reactive vs Template-driven (prefer Reactive). Do NOT use this skill for: - General conventions (see angular-conventions). - State management beyond forms (see angular-state-and-rx). - Routing (see angular-routing). - Testing forms (see angular-testing).

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

Organize, extract, prune, and verify Claude Code persistent memory files. Covers MEMORY.md as a concise index, topic extraction to dedicated files, staleness detection, accuracy verification against project state, the dual 200-line / 25KB load cap, and reachability of topic files from the index. Use when MEMORY.md is approaching either load cap, after a session produces durable insights worth preserving, when a topic section has grown beyond 10-15 lines and should be extracted, when project state has changed and memory entries may be stale, or before and after rewriting the index so that no topic file loses its only pointer.

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

Build or update a CONTEXT.md domain glossary for the current project. Establishes shared vocabulary with term definitions, avoid-aliases, and relationships so agents use consistent, concise language. This skill should be used when starting a new project, when domain terminology is inconsistent across sessions, when the user says "build a glossary", "define our terms", "shared vocabulary", or "domain language", or when an existing CONTEXT.md needs updating after new domain concepts emerge.

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

Create, audit, and maintain CLAUDE.md documentation files that configure Claude Code for projects. Use this skill when (1) initializing a new project with Claude Code configuration, (2) reviewing or improving existing CLAUDE.md files, (3) organizing project instructions using progressive disclosure patterns, (4) converting repeated instructions into permanent documentation, or (5) setting up agent_docs/ structures for larger codebases. Handles the WHAT/WHY/HOW framework, conciseness optimization, and file import patterns.

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

Capture reproducible screenshots from the currently booted iOS Simulator and turn them into three App Store marketing cards with validated dimensions and concise copy. Use after a successful Simulator build, during the two-minute proof lane, or when replacing prototype images with real app captures.

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

Use when current Odylith state needs a concise session brief.

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

Produce a concise session brief grounded in current Odylith state.

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

Distill books, documents, folders, or URLs into compact, practical Agent Skills. Use when source material should become either one reusable skill package or a split set of focused skills, each with a concise SKILL.md plus detailed references and examples.

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

Distill books, documents, folders, or URLs into compact, practical Agent Skills. Use when source material should become either one reusable skill package or a split set of focused skills, each with a concise SKILL.md plus detailed references and examples.

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

Create or audit a complete, concise, UI-ready website page content framework from verified business facts before visual design. Use to define page goals, customer decision flow, section order, realistic draft copy, content and evidence needs, CTAs, or page-family rules; do not use for visual design, HTML, SEO implementation, or platform code.

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

Use when creating or updating a pull request in this repository — how to fill in each section of the PR template with concise, reviewer-friendly content, including the behavior-change table.

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

Create a concise, evidence-backed implementation plan and save it to .agents/plans/Plan.md. Use when the user asks to plan a feature or task.

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

Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments

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

Explain what a piece of code does — a specific file, class, or method in close detail, or a user-facing flow as a concise system overview. What it does and why, not whether it's good.

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

Build a morning briefing ritual with Muse: overnight priorities, today's calendar, weather-aware planning, and top 3 focus items as a concise chat summary.

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

Write concise, role-specific cover letters that connect the candidate's story to the employer's needs.

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

Draft concise follow-up messages, nudges, reminders, and recap emails from open decisions, stale requests, or recent meetings. Use when the work is repetitive business writing with known context. Do not use for sensitive legal language, high-stakes negotiation, or board-level communication without review.

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

Create a concise daily briefing from calendar items, tasks, messages, and open decisions. Use at the start of a workday to identify priorities, risks, preparation needs, and follow-ups.

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

Write one-page executive briefs and decision memos that turn messy inputs into a concise recommendation, options, risks, decision ask, and next steps. Use when leaders need a fast read before approving budget, policy, vendor, headcount, or strategy changes. Do not use for long-form reports, slide design, or generic summarization without a decision.

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

Prevent common AI report pitfalls — bug blending, inflated threat models, and generic language. Train Claude with your best past reports for concise, technical submissions. Based on Critical Thinking Bug Bounty Podcast Episode 166.

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

Inspect scope and unexpected registry drift against the actual PR base and leave a concise final receipt. Use for "check for drift", "wrap up the pipeline", or the final stage; never silently discard unknown changes or infer a clean diff from validator success.

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

Use OpenClaw Manager (OCM) safely and correctly for OpenClaw environment lifecycle work, runtime installation/builds, release-shaped local builds, upgrades, migration/adoption, cloning existing user state, service supervision, gateway logs, dev worktrees, plugin testing, model/provider smoke tests, TUI/dashboard checks, cleanup, and concise reporting. Use whenever Codex is asked to use OCM, manage OpenClaw envs/runtimes/services, test OpenClaw with OCM, reproduce existing-user or new-user flows, or avoid breaking user state while working with OpenClaw.

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