'clean' 검색 결과

Write readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the user mentions "clean up this code", "this function is too long", "code smells", "naming conventions", "boy scout rule", "single responsibility", or "unit test quality". Also trigger when reviewing a pull request for readability, untangling a messy function, debating comment styles, or improving error-handling patterns. Covers SRP, comment discipline, formatting, and unit testing. For refactoring techniques, see refactoring-patterns. For architecture and dependency rules, see clean-architecture.

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

Use when targeting the Journal of Cleaner Production or deciding whether a cleaner-production/sustainability manuscript fits this venue. Encodes the journal's fit, the cleaner-production contribution and methodological-transparency bar, LCA/system-boundary expectations, house style, official-submission re-check, and desk-reject heuristics.

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

Identify stale and empty Claude Code sessions in the Agent Monitor and explain the cleanup endpoint (POST /api/settings/cleanup), always showing the exact list of what WOULD be removed before anything is deleted. Cleanup permanently deletes data, so this skill previews first and requires explicit user confirmation. Use when tidying the monitoring database.

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

Clean and normalize A-share financial data for modeling. Adapts the original clean-data-xls skill for Chinese financial statements, CAS conventions, and A-share data formats. Triggers on "A股数据清洗", "财务数据清洗", "clean financial data China", "数据清洗", or "normalize financial statements".

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

Clean-code engineering standards for writing, refactoring, and reviewing code in any programming language. Use this whenever the user asks to write clean code, follow clean-code principles, refactor for clarity, improve naming, reduce complexity or duplication, separate concerns, tighten error handling, work test-first or do TDD, or otherwise raise code quality, readability, and maintainability. Also use when writing or reviewing Operately APIs or Ecto queries. Apply these rules by default when producing or changing code for a quality-conscious user.

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

Use when a clinical CSV/Excel dataset needs profiling and cleaning before analysis (missing values, outliers, duplicates, type mismatches). Profiles, flags and generates cleaning code in three stages, each gated on the researcher's approval. Never auto-cleans.

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

Dead code and dependency cleanup, repo-wide: unused deps, unreferenced exports, unreachable code, orphaned files — removed only with tool evidence, in reversible waves. Runs on green main. For diff-scoped cleanup use absolute-simplify. Triggers on "absolute prune", "remove dead code", "find unused deps/exports", "what can we delete", "clean up orphaned files".

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

Review or improve code — one skill, four modes: bug/security review (default), performance, clean-code audit, slop cleanup. Pass mode:review|perf|clean|cleanup or infer. Don't use for writing features or generating tests (use test-coverage).

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

Two-agent cleanup pattern. Implementer works freely, then a dedicated cleanup agent removes unused imports, console.logs, commented-out code, dead code, and formatting issues. Produces a diff of what was cleaned.

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

Deletes merged git branches (local and remote) and flags stale unmerged branches for manual review. Use when user mentions "cleanup branches", "delete merged branches", "prune old branches", "remove stale branches", "branch cleanup", or runs /cleanup-branches command.

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

Use when designing, reviewing, or troubleshooting Salesforce duplicate prevention, matching rules, duplicate rules, and merge governance. Covers cleaning up duplicates that already exist at ordinary volume: merge sequencing, survivorship, stewardship ownership. Also covers the deployable MatchingRule / DuplicateRule metadata, the Alert-vs-Block action pair, DuplicateRecordSet reporting, and the Apex DMLOptions.DuplicateRuleHeader.allowSave bypass. Triggers: 'duplicate rule', 'matching rule', 'merge strategy', 'dedupe', 'survivorship', 'D&B', 'same contact twice', 'clean up duplicate records', 'clean up duplicate accounts', 'DUPLICATES_DETECTED', 'allowSave', 'FindDuplicates'. NOT for cleanup at volume — hundreds of thousands of records, batch merge jobs, DemandTools/Cloudingo — use data/large-scale-deduplication. NOT for which field values and child records the platform keeps in a merge - use data/record-merge-implications.

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

Default material, information-density hierarchy, clean-rendering, negative-prompt hygiene, and evidence-preserving photo-repair layer for IM2 / GPT Image 2 / gpt-image-2 / image_gen. Use for clean generation/redraws, artifact cleanup, focal-detail control, atmospheric depth, physically coherent light paths, air scattering, volumetric light, light ratio, material realism, architecture/terrain/hard-surface scene mass and structural grounding, and 企业/公司活动/门店/团队合影/商品/餐饮/证件文档照片修复. Preserve identity, headcount, placement, product facts, text, logo, QR, date, price, and scene evidence; prefer residual blur over invented restoration detail.

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

Review code for readability, then simplify it to be easy to follow and understand. Use this skill when the user wants to simplify code, improve readability, clean up for handoff, make code skimmable, reduce complexity, refactor for clarity, strip boilerplate, prepare code for future maintainers, or make a codebase easier to pick up. Trigger liberally — any request touching readability, simplification, cleanup, or "make this easier to understand" should use this skill. Also trigger when the user says things like "review this", "clean this up", "tidy this", "make this simpler", "reduce complexity", "flatten this", "strip the noise", or "I want to understand this code quickly next time I open it".

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

Inspects URL paths and proposes, tests, orders, and applies project-level path cleaning rules so dynamic segments (numeric IDs, UUIDs, slugs, dates) collapse into readable aliases. Use when the user says "clean the paths", "normalize URLs", "group similar pages", "too many distinct paths", "/users/123 and /users/456 are the same page", "set up path cleaning", or asks why a Web analytics or Paths breakdown is fragmented across thousands of nearly-identical URLs. Covers regex syntax (re2), alias placeholder convention, rule ordering, the test workflow, and applying rules via the project-settings-update MCP tool.

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

Delete old snapshots from _Archive/Snapshots/. Accepts a day threshold (default 180). Also `daily-intel [days]` mode — prune auto-generated n8n scanning surfaces (news briefs, X dashboards) from Daily Intel/ older than 90 days. Use when user says "clean", "clean snapshots", "delete old snapshots", "clean daily intel", or when /lint flags stale snapshots.

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

Delete old snapshots from _Archive/Snapshots/. Accepts a day threshold (default 180). Also `daily-intel [days]` mode — prune auto-generated n8n scanning surfaces (news briefs, X dashboards) from Daily Intel/ older than 90 days. Use when user says "clean", "clean snapshots", "delete old snapshots", "clean daily intel", or when $lint flags stale snapshots.

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

Undo a haircut trim. Puts back the skills, commands, subagents, MCP servers, hooks, plugins and files that haircut parked into a dated bag, using the receipt it wrote at the time. Use this skill whenever the user says undo the cleanup, undo the haircut, put my config back, restore what was trimmed, I need that MCP server again, that skill is gone and I want it back, roll the trim back, what is in the bag, or which files were moved. Use it also when something stopped working right after a config cleanup and they suspect the cleanup caused it, and whenever they ask how to reverse a config cleanup they regret.

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

팀에 맞는 Git 브랜치 전략을 선택하고 커밋과 풀 리퀘스트 작성 방식을 정리합니다. 이력 정리, 충돌 해결, 버전 태그와 릴리스 관리 절차도 다룹니다.

• 새 프로젝트의 브랜치 전략 선택
• 커밋 메시지와 풀 리퀘스트 설명 통일
• 풀 리퀘스트 전 로컬 이력 정리

Google Drive에서 문서·표·슬라이드를 찾아 내용을 확인하고 요약·편집·정리합니다. 계획서와 관리표를 통합하고 중복되거나 오래된 자료를 검토할 때도 사용합니다.

• 현재 사용하는 계획서 찾고 요약하기
• 공유 고객 목록 정리하기
• Google Slides로 가져와 정리하기

Claude Code 설정에서 중복 스킬, 오래된 메모리, 불필요한 권한을 점검합니다. 항목마다 확인을 받아 비활성화하거나 옮기고, 변경과 복원 방법을 기록합니다.

• 스킬을 대량 추가한 뒤 중복 확인
• 오래된 메모리와 불필요한 훅 점검
• 중복 권한 설정 정리

모바일 앱의 화면 시안과 이동 흐름을 이미지로 만듭니다. iOS와 Android 등의 특성을 반영하고 글자 가독성, 색상, 여러 화면의 일관성을 맞춥니다.

• 여러 화면으로 앱 기획 시각화
• 첫 사용 안내 화면 구상
• 로그인과 계정 복구 화면 검토

Implement and review GSAP animations in Vue, Nuxt, Svelte, and SvelteKit. It explains when to start animations, how to limit element selection to one component, and how to clean up when that component is removed.

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

• Adding GSAP animations to Vue or Svelte
• Reviewing animation cleanup when components are removed
• Keeping animations scoped to one component

Review safety-sensitive Mole changes using documented bug patterns. Check how cleanup targets are selected, whether commands have time limits, whether cancellation stops later work, and whether dry runs match actual deletion plans.

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

• Reviewing cleanup and uninstall safety
• Checking cancellation and command time limits
• Comparing dry-run plans with actual deletion

Build GSAP animations in Vue, Svelte, and related frameworks with clear setup and cleanup patterns. Scope element selection to each component, start animations after elements exist, and remove animations when the component is destroyed.

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

• Adding GSAP animations to Vue or Svelte components
• Keeping animations scoped to one component
• Cleaning up animations when components are removed