본문으로 건너뛰기
cccskills
무료GitHub에 공개

architect-conventions

Shared conventions for every SDLC development-phase architect agent: hard rules, code quality bar, workflow steps (superpowers invocation, spec reading, codebase exploration, verification), and the report/compact-summary contract. Architects load this skill first, then apply their stack-specific instructions on top.

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

AratKruglik/claude-sdlc

실행 점수 미검증

설치 방법 보기

포함된 파일(1)

  • SKILL.md4.1 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Architect Conventions (shared)

Every development-phase architect follows these rules. Your own agent definition adds stack-specific detection, conventions, and verification commands on top — where the two conflict, your agent definition wins.

Hard rules

  • Never delete files unless the spec explicitly asks for it.
  • Never modify .env, secrets/*, or ~/.claude/**.
  • Never disable existing tests to "make them pass". Mark as skip with a code comment if you genuinely can't fix in scope, and report it in your summary.
  • Never push branches or open PRs — that's the documentation phase's job.
  • Never add a dependency not declared in the BA spec or required by your implementation. Justify additions in DECISIONS.
  • Never edit lockfiles (package-lock.json, yarn.lock, pnpm-lock.yaml, composer.lock, poetry.lock, uv.lock, etc.) by hand.

Code quality bar

  • Follow existing patterns. Don't introduce a new way of doing things in scope of this feature.
  • No TODO/FIXME comments unless explicitly noting future work agreed upon by BA.
  • No commented-out code blocks.
  • No "in case we need it later" abstractions. YAGNI.
  • New deps via the project's package manager, pinned to a sane range (^x.y.z or stack equivalent). Never * or latest.
  • Match the existing styling/formatting approach. Don't introduce a new one.

Workflow steps

The orchestrator dispatches you in one of two passes: planning or implementation. Its base prompt tells you which pass you're in. In both:

  1. If superpowers is installed (no superpowers_unavailable flag in CONTEXT), invoke superpowers:using-superpowers via the Skill tool to discover available skills.
  2. Read the spec at docs/plans/{task_slug}/01-business-analysis.md (plus any earlier-aspect outputs listed in your CONTEXT trailer).
  3. Detect project shape — start from the project_shape: block in your CONTEXT trailer (package manager, runner prefix, test / lint / typecheck / format commands, test framework, CI, monorepo), computed once per session by scripts/detect-stack.sh. Run your agent definition's detection checklist only for keys that are null there — re-deriving a known answer is paid in tokens on every pass.
  4. Explore the codebase — Glob/Grep for the most similar existing feature; Read actual files and mirror their naming and patterns.
  5. Read CLAUDE.md — project conventions are sacred.
  6. Implement. Use Edit for existing files, Write for new ones. Keep changes minimal.
  7. Invoke convention skills the orchestrator passed that are relevant to the task.
  8. Verify with your agent definition's stack-specific commands (build, compile, import smoke test). Failures block completion. Formatters and the batched typecheck/lint are hook-driven — the stack plugin's PostToolUse hook formats every file you write and its SubagentStop hook runs the typecheck or linter once after you return, relaying failures to the orchestrator as a retry hint — so do not run those yourself.
  9. If superpowers is installed, invoke superpowers:verification-before-completion via the Skill tool before returning.

Deliverable contract

Write the detailed implementation report to docs/plans/{task_slug}/02-development{-aspect_suffix}.md covering: files created/modified (with purpose), dependencies added (with why), detected project shape, key design decisions with rationale, deviations from spec, manual verification performed, and open issues/blockers for the next phases.

Return value (COMPACT summary)

Return ONLY (≤3K tokens):

FILES CREATED: [paths with type tag]
FILES MODIFIED: [paths]
DEPS ADDED: [package@version, ... or "none"]
PROJECT SHAPE: [one line of detected key=value pairs]
DECISIONS: [3-5 bullets]
BLOCKERS: [empty or up to 3 lines]

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

angular-conventions

무료

Angular 18-21 project structure, standalone components vs NgModule, control flow (@if/@for/@switch + *ngIf/*ngFor legacy), decorators, dependency injection (inject() function), lifecycle hooks, pipes, Angular Universal SSR pointer. Use this skill to: - Detect project style (standalone vs NgModule) and apply matching patterns. - Pick correct decorators and DI approach. - Use modern control flow (@if/@for/@switch) in Angular 17+ projects. - Apply `inject()` function over constructor injection where appropriate. - Wire bootstrap correctly (bootstrapApplication for standalone, AppModule for legacy). Do NOT use this skill for: - State management (see angular-state-and-rx). - Routing (see angular-routing). - Forms (see angular-forms). - Testing (see angular-testing).

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

AratKruglik/claude-sdlc472026년 10월 17일 업데이트

angular-forms

무료

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).

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

AratKruglik/claude-sdlc472026년 10월 17일 업데이트

angular-routing

무료

Angular Router (built-in `@angular/router`) — route configuration for standalone and NgModule projects, functional guards (Angular 14.1+), lazy loading, route resolvers, typed params via signals/observables, programmatic navigation, route data and meta. Use this skill to: - Configure routes (standalone-style or NgModule-style). - Use functional guards (canActivate as function, preferred over class-based in 17+). - Lazy-load components or feature modules. - Implement auth guards via route meta + functional guards. - Read params/queries via `inject(ActivatedRoute)` + signals or RxJS. Do NOT use this skill for: - General conventions (see angular-conventions). - State management (see angular-state-and-rx). - Forms (see angular-forms). - Testing routes (see angular-testing).

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

AratKruglik/claude-sdlc472026년 10월 17일 업데이트

angular-state-and-rx

무료

State management for Angular 18-21: signals (signal/computed/effect), services-as-state, NgRx Store + Effects + Selectors, NgRx Component Store, NgRx Signals (newer signal-based store). RxJS essentials — operators, async pipe, takeUntilDestroyed, signal/observable interop. Use this skill to: - Pick the right state tool (signals / services / NgRx variant / vue-query equivalent). - Use signals correctly (signal/computed/effect — when each). - Build a Pinia-style service-as-state singleton. - Set up NgRx Store + Effects + Selectors. - Use RxJS without leaking subscriptions (async pipe, takeUntilDestroyed, Subject patterns). - Bridge signals ↔ observables via toSignal / toObservable. Do NOT use this skill for: - General Angular conventions (see angular-conventions). - Routing state (see angular-routing). - Form state (see angular-forms). - Testing state (see angular-testing).

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

AratKruglik/claude-sdlc472026년 10월 17일 업데이트

angular-testing

무료

Testing Angular 18-21: TestBed, component harnesses (@angular/cdk/testing), Karma+Jasmine (default historical) vs Jest (jest-preset-angular, modern), Angular Testing Library (RTL-style). HttpClient mocking via HttpTestingController. NgRx Effects testing. Cypress / Playwright e2e. Use this skill to: - Detect runner (Karma+Jasmine vs Jest) and configure correctly. - Write component tests with TestBed. - Use component harnesses for Material / custom UI components. - Mock HttpClient via provideHttpClientTesting + HttpTestingController. - Test signal-based inputs with componentRef.setInput(). - Test NgRx Effects with provideMockActions. Do NOT use this skill for: - General Angular conventions (see angular-conventions). - Routing patterns broadly (see angular-routing — covers testing routes briefly). - Form patterns broadly (see angular-forms).

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

AratKruglik/claude-sdlc472026년 10월 17일 업데이트

aspnet-conventions

무료

ASP.NET Core web framework conventions: Minimal API vs MVC controllers, Program.cs composition, DI lifetimes (Scoped/Singleton/Transient), Options pattern with IOptions<T>, middleware ordering (HTTPS redirect → routing → authentication → authorization), model binding and validation (FluentValidation / DataAnnotations), ProblemDetails error handling, structured logging with ILogger<T>, configuration layering (appsettings.json + environment variables + User Secrets), and health checks. Works alongside csharp-foundation:csharp-conventions and aspnet-core-plugin:efcore-patterns. Use this skill to: - Compose Program.cs correctly — register services, configure middleware in the right order, map endpoints. - Apply the Options pattern to avoid passing raw IConfiguration into services. - Write Minimal API endpoint groups with typed results and authorization. - Handle cross-cutting errors uniformly with ProblemDetails. - Configure structured logging and health checks for production readiness. Do NOT use this skill for: - EF Core entity configuration and migrations — see aspnet-core-plugin:efcore-patterns. - C# language idioms — see csharp-foundation:csharp-conventions. - Testing — see csharp-foundation:dotnet-testing.

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

AratKruglik/claude-sdlc472026년 10월 17일 업데이트

AratKruglik의 스킬 모두 보기

이 스킬의 문제 신고