無料GitHub で公開

ip-clean-room

Load before external product/design research, competitor comparison, clean-room implementation, or adding/updating code, packages, images, fonts, datasets, generated artifacts, or other dependencies whose source/provenance/license may affect outbound licensing; not for purely internal source use with no dependency change.

islamu-ngo/Event

インストール方法を見る

含まれるファイル（6）

SKILL.md4.4 KB
resources/audit-record-template.md1.5 KB
resources/dependency-license-gate.md2.5 KB
resources/index.md1.0 KB
resources/research-and-handoff.md2.3 KB
resources/sso-and-provenance-review.md1.8 KB

SKILL.md（原文）

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Must-Read Docs

Top 5 Invariants

Implementation context contains only sanitized functional requirements, repository-native design material, and permitted standards or interface facts, never third-party implementation source or source-derived representations.
Literal copying is zero-tolerance across code, SQL, migrations, tests, comments, documentation prose, assets, and generated artifacts.
The implementer independently designs naming, decomposition, data relationships, control flow, UI composition, tests, and documentation, then records an AFC/SSO review.
No dependency may block an intended ISLAMU outbound licensing path; the CLA never grants rights over third-party material, and exceptions require documented legal/distribution approval.
Externally informed work retains a source register, sanitized handoff, implementation-separation attestation, dependency decision, verification evidence, and PR/journal links without retaining restricted expression.

Top 5 Anti-Patterns

Source-bearing prompt: Supplying external code, snippets, ASTs, decompiled output, SQL, or internal structural notes contaminates the implementation context.
Cosmetic rewrite: Translating syntax or changing frameworks while preserving distinctive SSO remains non-literal copying risk.
CLA laundering: Treating a contributor signature as authority to copy or relicense third-party material invalidates provenance.
Scanner-as-counsel: Treating a passing automated license audit as proof of commercial-contract or assembled-distribution compatibility leaves material obligations unreviewed.
Anonymous benchmark report: Removing source identity rather than source expression destroys the audit trail and cannot support a clean-room handoff.

Minimal Examples

Clean-room handoff:
- Sources: titles/URLs/access dates only
- Observed behavior: inputs, outputs, errors, constraints
- Excluded: source, snippets, ASTs, internal names, copied prose/assets
- ISLAMU design: repository-native aggregate/workflow/API/HAL choices
- Attestation: implementation starts in a fresh source-free context

Dependency decision:
- Single supported build: compatible versions, deterministic locks
- Every distribution: retain each component's terms and required notices
- Block: any terms prevent an intended ISLAMU outbound offering

Verification Hooks

dotnet run .ci/scripts/validate-dependency-license-policy.cs -- .
dotnet test --project tests/Event.Architecture.Tests/Event.Architecture.Tests.csproj --configuration Release --verbosity quiet
git diff --check -- AGENTS.md docs/internal/legal docs/internal/QUICK_REFERENCE.md .agents/skills/ip-clean-room .agents/rules/ip-clean-room.md .agents/contract/intents.yaml .agents/skills/review-pr/SKILL.md .github/PULL_REQUEST_TEMPLATE.md dev/_journal/journal.md
Manual: complete SSO And Provenance Review and link the evidence in the PR.

Related Skills

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

ログインしてレビューを書く

同じリポジトリのスキル

概要と使いどころ

accessibility

無料

Load for Blazor/MudBlazor UI changes involving forms, dialogs, focus, keyboard navigation, landmarks, ARIA, color contrast, RTL-safe styling, or WCAG 2.2 AA tests; not for backend-only changes.

日本語の概要は準備中です。原文の説明を表示しています。