cc-best-practices
Improve Claude Code Workflows
Unclear prompts and crowded sessions reduce coding quality. This skill provides practical workflows for planning, verification, context control, automation, and independent review.
내 에이전트로 설치
이 요청을 에이전트에 복사하세요. 공식 Skill 페이지와 매니페스트가 포함되어 있습니다.
Review the Skillstore skill "cc-best-practices" from https://skillstore.io/skills/dboeckli-cc-best-practices.md and its manifest at https://skillstore.io/api/skills/dboeckli-cc-best-practices/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.에이전트는 계속해서 계획을 표시하고 보안 정책에서 요구하는 확인을 요청해야 합니다.
에이전트가 읽기 쉬운 리소스
AI 에이전트, 크롤러, 스크립트가 전체 페이지 대신 정리된 컨텍스트만 필요할 때 이 링크를 사용하세요.
테스트해 보기
"cc-best-practices" 사용 중입니다. Help me ask Claude to fix an intermittent login failure.
예상 결과:
Investigate login failures after session timeout. Inspect authentication refresh logic, add a reproducing test, implement the fix, and report test evidence.
"cc-best-practices" 사용 중입니다. My session is long, and Claude repeats the same mistake.
예상 결과:
- Record the missing constraint and any useful evidence.
- Clear the unrelated conversation context.
- Start again with the constraint, affected files, expected behavior, and a verification command.
"cc-best-practices" 사용 중입니다. How should my team review a large refactor?
예상 결과:
Use one session to implement the approved plan and another fresh session to inspect the diff, edge cases, and verification results.
보안 감사
중간 위험All 43 static alerts are false positives: the script uses fixed local validation commands, while the documentation alerts identify Markdown or benign examples. Two contextual risks remain because examples recommend sending logs to Claude and enabling broad unattended execution without adequate cautions.
확인된 보안 우려 사항 (2)
위험 요인
⚙️ 외부 명령어 (38)
📁 파일 시스템 접근 (2)
🌐 네트워크 접근 (1)
이 보고서 공유 및 인용
버전이 지정된 평가 보고서, 중립 배지, 임베드 카드 및 인용을 공유하세요. Skillstore는 근거를 보고하지만 이 Skill의 안전 여부를 판단하지 않습니다.
보고서 링크 복사
https://skillstore.io/skills/dboeckli-cc-best-practices/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown 배지
[](https://skillstore.io/skills/dboeckli-cc-best-practices?utm_source=security_passport_badge)HTML 배지
<a href="https://skillstore.io/skills/dboeckli-cc-best-practices?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/dboeckli-cc-best-practices/security.svg" alt="Skillstore security assessment" loading="lazy"></a>임베드 카드
<iframe src="https://skillstore.io/embed/skills/dboeckli-cc-best-practices.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>학술 인용 (APA · BibTeX · CFF)
APA 인용
dboeckli. (2026). cc-best-practices security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/dboeckli-cc-best-practices/audits/1BibTeX 인용
@techreport{dboeckli-dboeckli-cc-best-practices-2026,
author = {dboeckli},
title = {cc-best-practices security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/dboeckli-cc-best-practices/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "cc-best-practices security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "dboeckli"
date-released: "2026-09-26"
url: "https://skillstore.io/skills/dboeckli-cc-best-practices/audits/1"
identifiers:
- type: other
value: "skillstore:dboeckli-cc-best-practices:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore 점수
이 점수의 이유 증거 신뢰도: 중간만들 수 있는 것
Plan a Complex Change
Structure exploration, planning, implementation, and verification before editing several related files.
Standardize Team Instructions
Create a concise CLAUDE.md that records project-specific commands, architecture, testing rules, and repository conventions.
Scale Repetitive Analysis
Choose subagents, non-interactive commands, or parallel worktrees while preserving focused review and verification.
이 프롬프트를 사용해 보세요
Rewrite my request with explicit scope, relevant files, constraints, expected behavior, and one runnable verification step.
Explore the affected code without editing. Then produce a sequenced plan with dependencies, risks, files, and verification commands.
Identify missing context behind repeated failures. Draft a fresh prompt that states the constraint, example, scope, and acceptance test.
Design separate writer and reviewer sessions using worktrees. Define ownership, allowed tools, handoff evidence, and final integration checks.
모범 사례
- Provide a runnable check and request evidence from its output.
- Separate exploration, planning, implementation, and independent review for complex work.
- Keep persistent instructions short, project-specific, and necessary.
피하기
- Do not combine unrelated tasks in one crowded session.
- Do not continue correcting the same failure without improving the original context.
- Do not grant broad automation permissions without reviewing data exposure and persistent changes.
자주 묻는 질문
Does this skill modify my repository?
When should I use plan mode?
How should I verify generated code?
What belongs in CLAUDE.md?
Can Codex users apply this guidance?
Are the automation examples safe to run unchanged?
개발자 세부 정보
작성자
dboeckli라이선스
MIT
Skillstore 리비전
r1
버전 안내
작성자가 버전을 선언하지 않았습니다.
참조
1cda4003aa9ea65a9606af00b33e9c706ef03e62
유지보수 최신성
2026. 9. 30.
사용량
0 다운로드 · 0 조회
파일 구조