'maintenance' 검색 결과

Write, rewrite, review, and organize developer-facing documentation for web software projects. Use when creating or improving README files, docs homepages, quickstarts, tutorials, how-to guides, API/reference pages, conceptual explanations, migration guides, or troubleshooting content for frontend, backend, full-stack, SDK, API, or framework-based web products. This skill applies strong information architecture, task-first page structure, clear voice, runnable examples, version and prerequisite hygiene, accessibility rules, and docs-as-code maintenance habits. Do not use it for marketing copy, legal text, or non-technical customer-support articles.

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

Inspired by the ClawIntelligentMemory project, this skill ensures Kim Assistant's environment stays clean and its memory stays dense.

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

Use for design thinking, or when a product or service problem needs user understanding before solutions: "what do users really need?", "how might we...", "plan a discovery sprint", "validate this concept". Skip when the spec is frozen or the task is code maintenance.

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

Expert landscape designer transforming yards through photo mapping, 3D visualization, seasonal planning, and deep plant knowledge. Specializes in fast-growing privacy screens (knows arborvitae pitfalls), architecture-appropriate design, outdoor living spaces, and realistic maintenance expectations. Activate on "landscape design", "yard design", "garden planning", "plant selection", "privacy screen", "outdoor living", "backyard makeover", "arborvitae", "hedge", "fast growing tree", "landscaping ideas". NOT for interior design (use interior-design-expert), hardscape construction (consult contractors), or lawn care chemicals (consult local experts).

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

Implement Google's Material Design 3 (Material You) UI system. Primary: Jetpack Compose Material3 (MaterialTheme, components, adaptive layout). Also Flutter and limited web (@material/web, maintenance mode). Covers tokens, 30+ components, layout, theming, M3 Expressive (platform matrix), and accessibility. Use when: "material design", "MD3", "material you", "Jetpack Compose", "MaterialTheme", "material component", "md3 button".

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

Researches and compares free and open source software projects in a supplied domain, using either user-named candidates or a discovered shortlist. Use when evaluating FOSS alternatives, comparing GitHub popularity, maintenance, licences, domain fit, trade-offs, or producing a linked HTML comparison report.

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

Evaluate repeated code and consolidate duplication when a shared abstraction improves correctness or maintenance. Use after introducing similar logic or when repeated changes reveal a missing source of truth.

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

Systematic VPS cleanup — analyze files, categorize by importance, safely delete temporary/old data to free disk space

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

Review proposed abstractions, dependencies, and configuration for concrete consumers and maintenance cost when simplifying a design or checking overengineering.

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

Expert-level clinical engineering covering medical equipment management, hospital technology systems, healthcare IT integration, safety standards, and health technology assessment.

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

Use when configuring Laravel task scheduling — cron expressions, frequency helpers, overlap prevention, maintenance mode, or output handling.

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

Keep inherited changes narrow, correctly marked, traceable, and easy to rebase across repository layers.

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

Audit or update this Windows computer's fixed third-party Codex helper toolchain when the user requests local helper-tool maintenance. Always show the complete registered list and obtain confirmation for each update group; exclude Codex itself and general runtimes unless explicitly added.

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

文档出现腐化、冲突、重复、导航或归档混乱时使用。

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

Use for repository hygiene; reports governance maintenance findings and regenerates surfaces with --fix.

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

Namespace router → maintenance and code-quality chore skills. Use to pick the chore intent before invoking the matched concrete skill directly.

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

Periodic repository health check — install, full validation, unused-code scan, outdated/vulnerable dependencies, and docs drift — ending in a concise report and, when there are safe fixes, a single PR. Designed to run unattended from a scheduled routine; also usable on demand.

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

Show what maintenance robots already did today before you repair anything by hand: backups, reindexes, guards, quotas and what went stale. Use when deciding whether to rerun a backup, or when a command was blocked by a once-a-day gate. Triggers: /hk, /housekeeping, what was done today, should I run the backup, why was this blocked, show quotas, housekeeping status.

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

Restructure an always-loaded rules file such as CLAUDE.md or MEMORY.md: build a top block of key rules plus numbered categories, move rule bodies verbatim with a script that proves zero byte loss, fold heavy mechanics into trigger-plus-pointer form, then guards, a canary window and fleet rollout. For scheduled maintenance, not ad-hoc trimming. Triggers: "/canon-revision", "revise the canon".

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

Work through which package to add for a capability, and what each option costs — maintenance, licence, bundle weight, transitive risk, and whether the platform already does it. Use when someone needs a library for a job and has not picked one yet, when weighing two candidates, or when a package looks convenient but unmaintained.

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

Keep decision maps as concise routers from decisions to canonical documents and validation guardrails.

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

Knowledge base synthesized from the Guide to the Systems Engineering Body of Knowledge (SEBoK) v2.14 by the BKCASE Project. Use for the established systems-engineering canon: SE fundamentals and foundations (systems science, systems thinking, the systems approach, modelling/MBSE), the life cycle (ISO/IEC/IEEE 15288/24748/24774 process, development & agile approaches, model selection/tailoring), technical management, concept definition, architecture/realization (the Vee), V&V, maintenance/sustainment, SE standards, and the application contexts (product, service, enterprise, systems-of-systems, healthcare), plus enabling SE (business/team/individual), related disciplines, quality attributes/specialty engineering, implementation examples, and emerging knowledge. Good for grounding background, vocabulary, and prior-art positions across all eight SEBoK Parts. SCOPE LIMITS: this pack is SEBoK v2.14 only (released 2026-05-18); it synthesizes and signposts rather than reproducing the source — it does not reproduce ISO/IEC/IEEE standard text, is a curated guide (not a complete textbook), and is thin on AI-integration depth (Part 8 is a staging area, not settled practice). LICENCE: content is CC BY-NC-SA 3.0 — non-commercial use only, attribution to the BKCASE Project required, share-alike obligations carry forward.

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

Knowledge base from the NASA Fault Management Handbook (NASA-HDBK-1002, Draft 2, April 2012). Use for the systems-engineering discipline of designing what a system does when it fails — the fault/failure/anomaly vocabulary, the five FM strategies (two prevention strategies — design-time fault avoidance and operational failure avoidance — plus three tolerance strategies — failure masking, failure recovery, and goal change), the six FM process activities across NASA mission phases Pre-A to E, response-latency-versus-time-to-criticality (TTC) design trades, fault/failure containment regions and FEPPs, the four redundancy approaches, top-down FM requirements development, FM verification vs. validation, the seven dedicated FM milestone reviews (FMCR/FMARR/FMPDR/FMCDR/FMTRR/FMLRR/FMCERR), FM organizational structure, and mined NASA Lessons Learned. Space-mission oriented (flight/ground/operations); spacecraft examples throughout. IMPORTANT: built from an UNAPPROVED DRAFT — several sections (detailed architecture building blocks, the Assessment & Analysis guidance, and Operations & Maintenance) are placeholders in the source and are thin here. Thin on detailed FDIR algorithms, terrestrial/IT fault management, and any approved-standard terminology that may have changed since Draft 2.

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

Knowledge base from the NASA Schedule Management Handbook (2024 edition, Revision 2). Use for program/project schedule management of aerospace and large engineering efforts: the five sub-functions (Planning, Development, Assessment & Analysis, Maintenance & Control, Documentation & Communication); the Integrated Master Schedule (IMS) and the WBS/OBS/CBS breakdown structures; the Schedule Management Plan (SMP) and Basis of Estimate (BoE); Critical Path Method, logic, durations, float and margin; tiered schedule assessment (Requirements/Health/Basis checks, the Shock Test) and the Dimensions of Schedule Reliability; Schedule Risk Analysis (SRA), Integrated Cost-Schedule Risk Analysis (ICSRA), Monte Carlo, correlation, merge bias, and the Joint Confidence Level (JCL); baselining, replan vs. rebaseline, EVM schedule metrics (SPI, BEI, CEI, HMI, Earned Schedule, CPLI), and status/progress/forecast reporting. This is NASA's scheduling doctrine grounded in NPR 7120.5 and the GAO Schedule Assessment Guide. Thin on the underlying mechanics of CPM, statistics, and EVM (it points to companion handbooks); aerospace/space-flight-centric; anchored to the 2024 second edition.

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