@ryuenn3123/agentic-senior-core 1.9.0 → 1.9.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.agent-context/blueprints/mobile-app.md +21 -21
- package/.agent-context/policies/llm-judge-threshold.json +29 -20
- package/.agent-context/profiles/platform.md +13 -13
- package/.agent-context/profiles/regulated.md +13 -13
- package/.agent-context/profiles/startup.md +13 -13
- package/.agent-context/review-checklists/frontend-skill-parity.md +28 -28
- package/.agent-context/review-checklists/frontend-usability.md +33 -33
- package/.agent-context/review-checklists/release-operations.md +29 -29
- package/.agent-context/rules/security.md +92 -0
- package/.agent-context/skills/README.md +62 -62
- package/.agent-context/skills/backend/README.md +67 -67
- package/.agent-context/skills/backend/architecture.md +360 -360
- package/.agent-context/skills/backend/data-access.md +230 -230
- package/.agent-context/skills/backend/errors.md +137 -137
- package/.agent-context/skills/backend/validation.md +116 -116
- package/.agent-context/skills/backend.md +28 -28
- package/.agent-context/skills/cli/README.md +49 -49
- package/.agent-context/skills/cli/init.md +37 -37
- package/.agent-context/skills/cli/output.md +35 -35
- package/.agent-context/skills/cli/upgrade.md +37 -37
- package/.agent-context/skills/cli.md +28 -28
- package/.agent-context/skills/distribution/README.md +18 -18
- package/.agent-context/skills/distribution/compatibility.md +31 -31
- package/.agent-context/skills/distribution/publish.md +36 -36
- package/.agent-context/skills/distribution/rollback.md +31 -31
- package/.agent-context/skills/distribution.md +28 -28
- package/.agent-context/skills/frontend/README.md +35 -35
- package/.agent-context/skills/frontend/accessibility.md +107 -107
- package/.agent-context/skills/frontend/motion.md +66 -66
- package/.agent-context/skills/frontend/performance.md +62 -62
- package/.agent-context/skills/frontend/ui-architecture.md +128 -128
- package/.agent-context/skills/frontend.md +29 -29
- package/.agent-context/skills/fullstack/README.md +18 -18
- package/.agent-context/skills/fullstack/contracts.md +52 -52
- package/.agent-context/skills/fullstack/end-to-end.md +41 -41
- package/.agent-context/skills/fullstack/feature-slicing.md +64 -64
- package/.agent-context/skills/fullstack.md +26 -26
- package/.agent-context/skills/index.json +107 -107
- package/.agent-context/skills/review-quality/README.md +18 -18
- package/.agent-context/skills/review-quality/benchmark.md +29 -29
- package/.agent-context/skills/review-quality/planning.md +37 -37
- package/.agent-context/skills/review-quality/security.md +33 -33
- package/.agent-context/skills/review-quality.md +27 -27
- package/.agent-context/stacks/flutter.md +16 -16
- package/.agent-context/stacks/react-native.md +16 -16
- package/.agent-context/state/architecture-map.md +25 -25
- package/.agent-context/state/benchmark-analysis.json +431 -431
- package/.agent-context/state/benchmark-thresholds.json +10 -10
- package/.agent-context/state/benchmark-watchlist.json +19 -19
- package/.agent-context/state/dependency-map.md +32 -32
- package/.agent-context/state/onboarding-report.json +39 -0
- package/.agent-context/state/skill-platform.json +38 -38
- package/.agent-override.md +36 -36
- package/.cursorrules +3718 -140
- package/.github/ISSUE_TEMPLATE/v1.7-frontend-work-item.yml +54 -54
- package/.github/workflows/benchmark-detection.yml +38 -38
- package/.github/workflows/benchmark-intelligence.yml +50 -50
- package/.github/workflows/frontend-usability-gate.yml +36 -36
- package/.github/workflows/publish.yml +32 -0
- package/.github/workflows/release-gate.yml +32 -32
- package/.github/workflows/sbom-compliance.yml +32 -32
- package/.windsurfrules +3718 -106
- package/AGENTS.md +181 -181
- package/README.md +318 -318
- package/bin/agentic-senior-core.js +61 -1556
- package/lib/cli/commands/init.mjs +339 -0
- package/lib/cli/commands/launch.mjs +81 -0
- package/lib/cli/commands/upgrade.mjs +165 -0
- package/lib/cli/compiler.mjs +204 -0
- package/lib/cli/constants.mjs +136 -0
- package/lib/cli/detector.mjs +211 -0
- package/lib/cli/profile-packs.mjs +94 -0
- package/lib/cli/skill-selector.mjs +210 -0
- package/lib/cli/utils.mjs +227 -0
- package/mcp.json +92 -92
- package/package.json +3 -1
- package/scripts/benchmark-gate.mjs +121 -121
- package/scripts/benchmark-intelligence.mjs +140 -140
- package/scripts/detection-benchmark.mjs +138 -138
- package/scripts/frontend-usability-audit.mjs +87 -87
- package/scripts/generate-sbom.mjs +61 -61
- package/scripts/init-project.ps1 +104 -104
- package/scripts/llm-judge.mjs +664 -664
- package/scripts/release-gate.mjs +116 -116
- package/scripts/skill-tier-policy.mjs +75 -75
- package/scripts/validate.mjs +636 -636
|
@@ -1,38 +1,38 @@
|
|
|
1
|
-
# Init Flow
|
|
2
|
-
|
|
3
|
-
Tier: ADVANCE
|
|
4
|
-
|
|
5
|
-
Initialization commands must be deterministic, reversible where possible, and explicit about filesystem mutations.
|
|
6
|
-
|
|
7
|
-
## Design Principles
|
|
8
|
-
|
|
9
|
-
- Predictable output for identical input flags.
|
|
10
|
-
- Safe defaults when users omit options.
|
|
11
|
-
- Preflight summary before any file write.
|
|
12
|
-
|
|
13
|
-
## Required Init Sequence
|
|
14
|
-
|
|
15
|
-
1. Validate prerequisites (runtime, permissions, existing files).
|
|
16
|
-
2. Resolve stack/profile/blueprint selection.
|
|
17
|
-
3. Print write plan summary.
|
|
18
|
-
4. Apply scaffold atomically.
|
|
19
|
-
5. Emit machine-readable onboarding report.
|
|
20
|
-
|
|
21
|
-
## Write Safety
|
|
22
|
-
|
|
23
|
-
- Refuse to overwrite existing files without explicit flag.
|
|
24
|
-
- Use idempotent initialization where feasible.
|
|
25
|
-
- Keep generated files grouped by feature intent, not random dump.
|
|
26
|
-
|
|
27
|
-
## Anti-Patterns
|
|
28
|
-
|
|
29
|
-
- Hidden writes without disclosure.
|
|
30
|
-
- Interactive-only flow with no non-interactive equivalent.
|
|
31
|
-
- Ambiguous defaults that vary by environment.
|
|
32
|
-
|
|
33
|
-
## Review Checklist
|
|
34
|
-
|
|
35
|
-
- [ ] Preflight checks are explicit and actionable.
|
|
36
|
-
- [ ] Generated file set is deterministic.
|
|
37
|
-
- [ ] Dry-run preview exists for init planning.
|
|
1
|
+
# Init Flow
|
|
2
|
+
|
|
3
|
+
Tier: ADVANCE
|
|
4
|
+
|
|
5
|
+
Initialization commands must be deterministic, reversible where possible, and explicit about filesystem mutations.
|
|
6
|
+
|
|
7
|
+
## Design Principles
|
|
8
|
+
|
|
9
|
+
- Predictable output for identical input flags.
|
|
10
|
+
- Safe defaults when users omit options.
|
|
11
|
+
- Preflight summary before any file write.
|
|
12
|
+
|
|
13
|
+
## Required Init Sequence
|
|
14
|
+
|
|
15
|
+
1. Validate prerequisites (runtime, permissions, existing files).
|
|
16
|
+
2. Resolve stack/profile/blueprint selection.
|
|
17
|
+
3. Print write plan summary.
|
|
18
|
+
4. Apply scaffold atomically.
|
|
19
|
+
5. Emit machine-readable onboarding report.
|
|
20
|
+
|
|
21
|
+
## Write Safety
|
|
22
|
+
|
|
23
|
+
- Refuse to overwrite existing files without explicit flag.
|
|
24
|
+
- Use idempotent initialization where feasible.
|
|
25
|
+
- Keep generated files grouped by feature intent, not random dump.
|
|
26
|
+
|
|
27
|
+
## Anti-Patterns
|
|
28
|
+
|
|
29
|
+
- Hidden writes without disclosure.
|
|
30
|
+
- Interactive-only flow with no non-interactive equivalent.
|
|
31
|
+
- Ambiguous defaults that vary by environment.
|
|
32
|
+
|
|
33
|
+
## Review Checklist
|
|
34
|
+
|
|
35
|
+
- [ ] Preflight checks are explicit and actionable.
|
|
36
|
+
- [ ] Generated file set is deterministic.
|
|
37
|
+
- [ ] Dry-run preview exists for init planning.
|
|
38
38
|
- [ ] Exit codes distinguish validation vs runtime failures.
|
|
@@ -1,36 +1,36 @@
|
|
|
1
|
-
# Machine-Readable Output
|
|
2
|
-
|
|
3
|
-
Tier: ADVANCE
|
|
4
|
-
|
|
5
|
-
CLI output must support both human readability and automation reliability.
|
|
6
|
-
|
|
7
|
-
## Output Contract
|
|
8
|
-
|
|
9
|
-
- Human mode: concise narrative and actionable next steps.
|
|
10
|
-
- JSON mode: deterministic schema, stable field names, and clear status.
|
|
11
|
-
|
|
12
|
-
## JSON Schema Guidelines
|
|
13
|
-
|
|
14
|
-
- Include `version`, `timestamp`, `status`, and `summary`.
|
|
15
|
-
- Include `artifacts` list for produced files.
|
|
16
|
-
- Include `errors` array with machine-readable codes.
|
|
17
|
-
- Avoid embedding plain stack traces in public payloads.
|
|
18
|
-
|
|
19
|
-
## Exit Code Conventions
|
|
20
|
-
|
|
21
|
-
- `0`: success
|
|
22
|
-
- `1`: validation or runtime failure
|
|
23
|
-
- `2`: policy/gate failure
|
|
24
|
-
|
|
25
|
-
## Determinism Rules
|
|
26
|
-
|
|
27
|
-
- Stable key ordering where practical.
|
|
28
|
-
- No random IDs unless explicitly requested.
|
|
29
|
-
- Timestamps in ISO 8601 format.
|
|
30
|
-
|
|
31
|
-
## Review Checklist
|
|
32
|
-
|
|
33
|
-
- [ ] JSON output passes schema validation.
|
|
34
|
-
- [ ] Exit codes match documented behavior.
|
|
35
|
-
- [ ] Error payload includes code and remediation hint.
|
|
1
|
+
# Machine-Readable Output
|
|
2
|
+
|
|
3
|
+
Tier: ADVANCE
|
|
4
|
+
|
|
5
|
+
CLI output must support both human readability and automation reliability.
|
|
6
|
+
|
|
7
|
+
## Output Contract
|
|
8
|
+
|
|
9
|
+
- Human mode: concise narrative and actionable next steps.
|
|
10
|
+
- JSON mode: deterministic schema, stable field names, and clear status.
|
|
11
|
+
|
|
12
|
+
## JSON Schema Guidelines
|
|
13
|
+
|
|
14
|
+
- Include `version`, `timestamp`, `status`, and `summary`.
|
|
15
|
+
- Include `artifacts` list for produced files.
|
|
16
|
+
- Include `errors` array with machine-readable codes.
|
|
17
|
+
- Avoid embedding plain stack traces in public payloads.
|
|
18
|
+
|
|
19
|
+
## Exit Code Conventions
|
|
20
|
+
|
|
21
|
+
- `0`: success
|
|
22
|
+
- `1`: validation or runtime failure
|
|
23
|
+
- `2`: policy/gate failure
|
|
24
|
+
|
|
25
|
+
## Determinism Rules
|
|
26
|
+
|
|
27
|
+
- Stable key ordering where practical.
|
|
28
|
+
- No random IDs unless explicitly requested.
|
|
29
|
+
- Timestamps in ISO 8601 format.
|
|
30
|
+
|
|
31
|
+
## Review Checklist
|
|
32
|
+
|
|
33
|
+
- [ ] JSON output passes schema validation.
|
|
34
|
+
- [ ] Exit codes match documented behavior.
|
|
35
|
+
- [ ] Error payload includes code and remediation hint.
|
|
36
36
|
- [ ] Human output remains concise and useful.
|
|
@@ -1,38 +1,38 @@
|
|
|
1
|
-
# Upgrade Flow
|
|
2
|
-
|
|
3
|
-
Tier: ADVANCE
|
|
4
|
-
|
|
5
|
-
Upgrade commands must prioritize compatibility, transparency, and recovery.
|
|
6
|
-
|
|
7
|
-
## Required Controls
|
|
8
|
-
|
|
9
|
-
- Dry-run mode to preview changes.
|
|
10
|
-
- Compatibility checks before mutation.
|
|
11
|
-
- Backup or rollback path for critical files.
|
|
12
|
-
|
|
13
|
-
## Upgrade Sequence
|
|
14
|
-
|
|
15
|
-
1. Read current version and target version.
|
|
16
|
-
2. Evaluate compatibility matrix.
|
|
17
|
-
3. Produce migration plan (files to add/change/remove).
|
|
18
|
-
4. Execute with transactional mindset.
|
|
19
|
-
5. Emit post-upgrade report with changed artifacts.
|
|
20
|
-
|
|
21
|
-
## Failure Handling
|
|
22
|
-
|
|
23
|
-
- On partial failure, rollback modified artifacts or provide deterministic recovery instructions.
|
|
24
|
-
- Never leave silent half-upgraded state.
|
|
25
|
-
- Exit with explicit status code and structured error payload.
|
|
26
|
-
|
|
27
|
-
## Anti-Patterns
|
|
28
|
-
|
|
29
|
-
- In-place mutation without preview.
|
|
30
|
-
- Version bump without migration note.
|
|
31
|
-
- Breaking changes in minor release without contract guard.
|
|
32
|
-
|
|
33
|
-
## Review Checklist
|
|
34
|
-
|
|
35
|
-
- [ ] Dry-run output is complete and stable.
|
|
36
|
-
- [ ] Upgrade report captures all changed files.
|
|
37
|
-
- [ ] Rollback path is tested.
|
|
1
|
+
# Upgrade Flow
|
|
2
|
+
|
|
3
|
+
Tier: ADVANCE
|
|
4
|
+
|
|
5
|
+
Upgrade commands must prioritize compatibility, transparency, and recovery.
|
|
6
|
+
|
|
7
|
+
## Required Controls
|
|
8
|
+
|
|
9
|
+
- Dry-run mode to preview changes.
|
|
10
|
+
- Compatibility checks before mutation.
|
|
11
|
+
- Backup or rollback path for critical files.
|
|
12
|
+
|
|
13
|
+
## Upgrade Sequence
|
|
14
|
+
|
|
15
|
+
1. Read current version and target version.
|
|
16
|
+
2. Evaluate compatibility matrix.
|
|
17
|
+
3. Produce migration plan (files to add/change/remove).
|
|
18
|
+
4. Execute with transactional mindset.
|
|
19
|
+
5. Emit post-upgrade report with changed artifacts.
|
|
20
|
+
|
|
21
|
+
## Failure Handling
|
|
22
|
+
|
|
23
|
+
- On partial failure, rollback modified artifacts or provide deterministic recovery instructions.
|
|
24
|
+
- Never leave silent half-upgraded state.
|
|
25
|
+
- Exit with explicit status code and structured error payload.
|
|
26
|
+
|
|
27
|
+
## Anti-Patterns
|
|
28
|
+
|
|
29
|
+
- In-place mutation without preview.
|
|
30
|
+
- Version bump without migration note.
|
|
31
|
+
- Breaking changes in minor release without contract guard.
|
|
32
|
+
|
|
33
|
+
## Review Checklist
|
|
34
|
+
|
|
35
|
+
- [ ] Dry-run output is complete and stable.
|
|
36
|
+
- [ ] Upgrade report captures all changed files.
|
|
37
|
+
- [ ] Rollback path is tested.
|
|
38
38
|
- [ ] Compatibility failures block mutation.
|
|
@@ -1,29 +1,29 @@
|
|
|
1
|
-
# CLI Skill Pack
|
|
2
|
-
|
|
3
|
-
Default tier: `advance`
|
|
4
|
-
|
|
5
|
-
## Purpose
|
|
6
|
-
Create smart command-line workflows that guide users efficiently and safely.
|
|
7
|
-
|
|
8
|
-
## In Scope
|
|
9
|
-
- Interactive initialization and upgrade flows
|
|
10
|
-
- Safe defaults and confirmation steps
|
|
11
|
-
- Machine-readable output for automation
|
|
12
|
-
- Validation and self-healing hooks
|
|
13
|
-
- Cross-platform shell behavior
|
|
14
|
-
|
|
15
|
-
## Must-Have Checks
|
|
16
|
-
- Explicit command help and examples
|
|
17
|
-
- Deterministic output format for automation
|
|
18
|
-
- Safe destructive-action guards
|
|
19
|
-
- Validation before mutation
|
|
20
|
-
- Exit codes reflect success and failure clearly
|
|
21
|
-
|
|
22
|
-
## Evidence
|
|
23
|
-
- CLI smoke tests
|
|
24
|
-
- Machine-readable report output
|
|
25
|
-
- Upgrade dry-run output
|
|
26
|
-
- Cross-platform execution notes
|
|
27
|
-
|
|
28
|
-
## Fallback
|
|
1
|
+
# CLI Skill Pack
|
|
2
|
+
|
|
3
|
+
Default tier: `advance`
|
|
4
|
+
|
|
5
|
+
## Purpose
|
|
6
|
+
Create smart command-line workflows that guide users efficiently and safely.
|
|
7
|
+
|
|
8
|
+
## In Scope
|
|
9
|
+
- Interactive initialization and upgrade flows
|
|
10
|
+
- Safe defaults and confirmation steps
|
|
11
|
+
- Machine-readable output for automation
|
|
12
|
+
- Validation and self-healing hooks
|
|
13
|
+
- Cross-platform shell behavior
|
|
14
|
+
|
|
15
|
+
## Must-Have Checks
|
|
16
|
+
- Explicit command help and examples
|
|
17
|
+
- Deterministic output format for automation
|
|
18
|
+
- Safe destructive-action guards
|
|
19
|
+
- Validation before mutation
|
|
20
|
+
- Exit codes reflect success and failure clearly
|
|
21
|
+
|
|
22
|
+
## Evidence
|
|
23
|
+
- CLI smoke tests
|
|
24
|
+
- Machine-readable report output
|
|
25
|
+
- Upgrade dry-run output
|
|
26
|
+
- Cross-platform execution notes
|
|
27
|
+
|
|
28
|
+
## Fallback
|
|
29
29
|
- Standard mode can remain available for compatibility, but advance is the default user experience.
|
|
@@ -1,19 +1,19 @@
|
|
|
1
|
-
# Distribution Engineering Skills
|
|
2
|
-
|
|
3
|
-
Default tier: `expert`
|
|
4
|
-
|
|
5
|
-
This domain governs release packaging, compatibility policy, and rollback readiness.
|
|
6
|
-
|
|
7
|
-
## Topics
|
|
8
|
-
- [Publish Hygiene](publish.md) - Package integrity, provenance, and release evidence
|
|
9
|
-
- [Rollback](rollback.md) - Recovery-first release operations
|
|
10
|
-
- [Compatibility](compatibility.md) - Runtime/tooling support policy and guardrails
|
|
11
|
-
|
|
12
|
-
## Operating Model
|
|
13
|
-
- Use `expert` as the default distribution tier.
|
|
14
|
-
- Block release if rollback and compatibility guarantees are not verified.
|
|
15
|
-
|
|
16
|
-
## Above-Line Additions
|
|
17
|
-
- Release gates tied to benchmark and compatibility checks.
|
|
18
|
-
- Supply-chain artifacts (SBOM/provenance) as first-class outputs.
|
|
1
|
+
# Distribution Engineering Skills
|
|
2
|
+
|
|
3
|
+
Default tier: `expert`
|
|
4
|
+
|
|
5
|
+
This domain governs release packaging, compatibility policy, and rollback readiness.
|
|
6
|
+
|
|
7
|
+
## Topics
|
|
8
|
+
- [Publish Hygiene](publish.md) - Package integrity, provenance, and release evidence
|
|
9
|
+
- [Rollback](rollback.md) - Recovery-first release operations
|
|
10
|
+
- [Compatibility](compatibility.md) - Runtime/tooling support policy and guardrails
|
|
11
|
+
|
|
12
|
+
## Operating Model
|
|
13
|
+
- Use `expert` as the default distribution tier.
|
|
14
|
+
- Block release if rollback and compatibility guarantees are not verified.
|
|
15
|
+
|
|
16
|
+
## Above-Line Additions
|
|
17
|
+
- Release gates tied to benchmark and compatibility checks.
|
|
18
|
+
- Supply-chain artifacts (SBOM/provenance) as first-class outputs.
|
|
19
19
|
- Explicit rollback drills before critical releases.
|
|
@@ -1,32 +1,32 @@
|
|
|
1
|
-
# Compatibility
|
|
2
|
-
|
|
3
|
-
Tier: ADVANCE
|
|
4
|
-
|
|
5
|
-
Compatibility policy prevents shipping builds that break on supported runtimes or tooling ecosystems.
|
|
6
|
-
|
|
7
|
-
## Compatibility Matrix
|
|
8
|
-
|
|
9
|
-
Define supported combinations explicitly:
|
|
10
|
-
- Runtime versions (Node, Python, Java, etc.)
|
|
11
|
-
- OS/platform scope
|
|
12
|
-
- IDE/editor integration versions
|
|
13
|
-
- Dependency constraints
|
|
14
|
-
|
|
15
|
-
## Gate Strategy
|
|
16
|
-
|
|
17
|
-
- Validate package against supported runtime matrix in CI.
|
|
18
|
-
- Block release on unsupported runtime regressions.
|
|
19
|
-
- Mark deprecated support windows and removal timeline.
|
|
20
|
-
|
|
21
|
-
## Breaking Change Protocol
|
|
22
|
-
|
|
23
|
-
- Major version for incompatible behavior.
|
|
24
|
-
- Migration notes for changed defaults.
|
|
25
|
-
- Transitional compatibility period when feasible.
|
|
26
|
-
|
|
27
|
-
## Review Checklist
|
|
28
|
-
|
|
29
|
-
- [ ] Supported runtime matrix is current and tested.
|
|
30
|
-
- [ ] Incompatible changes are versioned correctly.
|
|
31
|
-
- [ ] Migration notes exist for user-impacting changes.
|
|
1
|
+
# Compatibility
|
|
2
|
+
|
|
3
|
+
Tier: ADVANCE
|
|
4
|
+
|
|
5
|
+
Compatibility policy prevents shipping builds that break on supported runtimes or tooling ecosystems.
|
|
6
|
+
|
|
7
|
+
## Compatibility Matrix
|
|
8
|
+
|
|
9
|
+
Define supported combinations explicitly:
|
|
10
|
+
- Runtime versions (Node, Python, Java, etc.)
|
|
11
|
+
- OS/platform scope
|
|
12
|
+
- IDE/editor integration versions
|
|
13
|
+
- Dependency constraints
|
|
14
|
+
|
|
15
|
+
## Gate Strategy
|
|
16
|
+
|
|
17
|
+
- Validate package against supported runtime matrix in CI.
|
|
18
|
+
- Block release on unsupported runtime regressions.
|
|
19
|
+
- Mark deprecated support windows and removal timeline.
|
|
20
|
+
|
|
21
|
+
## Breaking Change Protocol
|
|
22
|
+
|
|
23
|
+
- Major version for incompatible behavior.
|
|
24
|
+
- Migration notes for changed defaults.
|
|
25
|
+
- Transitional compatibility period when feasible.
|
|
26
|
+
|
|
27
|
+
## Review Checklist
|
|
28
|
+
|
|
29
|
+
- [ ] Supported runtime matrix is current and tested.
|
|
30
|
+
- [ ] Incompatible changes are versioned correctly.
|
|
31
|
+
- [ ] Migration notes exist for user-impacting changes.
|
|
32
32
|
- [ ] CI verifies compatibility before publish.
|
|
@@ -1,37 +1,37 @@
|
|
|
1
|
-
# Publish Hygiene
|
|
2
|
-
|
|
3
|
-
Tier: EXPERT
|
|
4
|
-
|
|
5
|
-
Publishing should be repeatable, auditable, and minimal in surface area.
|
|
6
|
-
|
|
7
|
-
## Pre-Publish Gates
|
|
8
|
-
|
|
9
|
-
- Validate package contents and metadata.
|
|
10
|
-
- Run tests and policy validators.
|
|
11
|
-
- Confirm version/changelog consistency.
|
|
12
|
-
- Generate SBOM and provenance artifacts.
|
|
13
|
-
|
|
14
|
-
## Package Surface Control
|
|
15
|
-
|
|
16
|
-
- Use explicit allow-list for publish files.
|
|
17
|
-
- Exclude internal scripts, test fixtures, and local configs.
|
|
18
|
-
- Verify CLI entry points and executable permissions.
|
|
19
|
-
|
|
20
|
-
## Ownership and Provenance
|
|
21
|
-
|
|
22
|
-
- Ensure publisher identity is controlled.
|
|
23
|
-
- Record commit SHA and release timestamp.
|
|
24
|
-
- Attach generated reports (gate, benchmark, SBOM) to release artifacts.
|
|
25
|
-
|
|
26
|
-
## Failure Policy
|
|
27
|
-
|
|
28
|
-
- Abort publish on failing quality gate.
|
|
29
|
-
- Abort publish on unresolved high-severity security findings.
|
|
30
|
-
- Abort publish on missing changelog entry.
|
|
31
|
-
|
|
32
|
-
## Review Checklist
|
|
33
|
-
|
|
34
|
-
- [ ] Package contents match expected release manifest.
|
|
35
|
-
- [ ] Quality and security gates passed.
|
|
36
|
-
- [ ] Version and changelog are aligned.
|
|
1
|
+
# Publish Hygiene
|
|
2
|
+
|
|
3
|
+
Tier: EXPERT
|
|
4
|
+
|
|
5
|
+
Publishing should be repeatable, auditable, and minimal in surface area.
|
|
6
|
+
|
|
7
|
+
## Pre-Publish Gates
|
|
8
|
+
|
|
9
|
+
- Validate package contents and metadata.
|
|
10
|
+
- Run tests and policy validators.
|
|
11
|
+
- Confirm version/changelog consistency.
|
|
12
|
+
- Generate SBOM and provenance artifacts.
|
|
13
|
+
|
|
14
|
+
## Package Surface Control
|
|
15
|
+
|
|
16
|
+
- Use explicit allow-list for publish files.
|
|
17
|
+
- Exclude internal scripts, test fixtures, and local configs.
|
|
18
|
+
- Verify CLI entry points and executable permissions.
|
|
19
|
+
|
|
20
|
+
## Ownership and Provenance
|
|
21
|
+
|
|
22
|
+
- Ensure publisher identity is controlled.
|
|
23
|
+
- Record commit SHA and release timestamp.
|
|
24
|
+
- Attach generated reports (gate, benchmark, SBOM) to release artifacts.
|
|
25
|
+
|
|
26
|
+
## Failure Policy
|
|
27
|
+
|
|
28
|
+
- Abort publish on failing quality gate.
|
|
29
|
+
- Abort publish on unresolved high-severity security findings.
|
|
30
|
+
- Abort publish on missing changelog entry.
|
|
31
|
+
|
|
32
|
+
## Review Checklist
|
|
33
|
+
|
|
34
|
+
- [ ] Package contents match expected release manifest.
|
|
35
|
+
- [ ] Quality and security gates passed.
|
|
36
|
+
- [ ] Version and changelog are aligned.
|
|
37
37
|
- [ ] Provenance artifacts are generated and stored.
|
|
@@ -1,32 +1,32 @@
|
|
|
1
|
-
# Rollback
|
|
2
|
-
|
|
3
|
-
Tier: EXPERT
|
|
4
|
-
|
|
5
|
-
Rollback is a mandatory release capability, not an afterthought.
|
|
6
|
-
|
|
7
|
-
## Rollback Readiness
|
|
8
|
-
|
|
9
|
-
- Define rollback trigger conditions before release.
|
|
10
|
-
- Keep previous stable artifact available for immediate redeploy.
|
|
11
|
-
- Preserve migration rollback scripts for data-affecting changes.
|
|
12
|
-
|
|
13
|
-
## Rollback Flow
|
|
14
|
-
|
|
15
|
-
1. Detect failure signal (error spike, failed SLO, functional regression).
|
|
16
|
-
2. Freeze new rollout.
|
|
17
|
-
3. Re-deploy previous known-good version.
|
|
18
|
-
4. Verify health checks and key journeys.
|
|
19
|
-
5. Publish incident summary with root-cause owner.
|
|
20
|
-
|
|
21
|
-
## Data Change Safety
|
|
22
|
-
|
|
23
|
-
- Use backward-compatible migrations for forward and rollback paths.
|
|
24
|
-
- Avoid destructive schema operations in same release as code cutover.
|
|
25
|
-
- Validate rollback on staging with production-like data shape.
|
|
26
|
-
|
|
27
|
-
## Review Checklist
|
|
28
|
-
|
|
29
|
-
- [ ] Rollback plan documented and tested.
|
|
30
|
-
- [ ] Previous release artifact retained.
|
|
31
|
-
- [ ] Data migration rollback path verified.
|
|
1
|
+
# Rollback
|
|
2
|
+
|
|
3
|
+
Tier: EXPERT
|
|
4
|
+
|
|
5
|
+
Rollback is a mandatory release capability, not an afterthought.
|
|
6
|
+
|
|
7
|
+
## Rollback Readiness
|
|
8
|
+
|
|
9
|
+
- Define rollback trigger conditions before release.
|
|
10
|
+
- Keep previous stable artifact available for immediate redeploy.
|
|
11
|
+
- Preserve migration rollback scripts for data-affecting changes.
|
|
12
|
+
|
|
13
|
+
## Rollback Flow
|
|
14
|
+
|
|
15
|
+
1. Detect failure signal (error spike, failed SLO, functional regression).
|
|
16
|
+
2. Freeze new rollout.
|
|
17
|
+
3. Re-deploy previous known-good version.
|
|
18
|
+
4. Verify health checks and key journeys.
|
|
19
|
+
5. Publish incident summary with root-cause owner.
|
|
20
|
+
|
|
21
|
+
## Data Change Safety
|
|
22
|
+
|
|
23
|
+
- Use backward-compatible migrations for forward and rollback paths.
|
|
24
|
+
- Avoid destructive schema operations in same release as code cutover.
|
|
25
|
+
- Validate rollback on staging with production-like data shape.
|
|
26
|
+
|
|
27
|
+
## Review Checklist
|
|
28
|
+
|
|
29
|
+
- [ ] Rollback plan documented and tested.
|
|
30
|
+
- [ ] Previous release artifact retained.
|
|
31
|
+
- [ ] Data migration rollback path verified.
|
|
32
32
|
- [ ] Health checks confirm rollback success.
|
|
@@ -1,29 +1,29 @@
|
|
|
1
|
-
# Distribution Skill Pack
|
|
2
|
-
|
|
3
|
-
Default tier: `expert`
|
|
4
|
-
|
|
5
|
-
## Purpose
|
|
6
|
-
Protect package installation and release distribution with transactional safety.
|
|
7
|
-
|
|
8
|
-
## In Scope
|
|
9
|
-
- Package validation
|
|
10
|
-
- Backup and rollback
|
|
11
|
-
- Compatibility checks
|
|
12
|
-
- Forbidden-file detection
|
|
13
|
-
- Publish hygiene and provenance
|
|
14
|
-
|
|
15
|
-
## Must-Have Checks
|
|
16
|
-
- Preflight validation before installation or publish
|
|
17
|
-
- Backup point before mutating user state
|
|
18
|
-
- Automatic rollback on failure
|
|
19
|
-
- Compatibility manifest present
|
|
20
|
-
- Evidence bundle attached to release
|
|
21
|
-
|
|
22
|
-
## Evidence
|
|
23
|
-
- Install validation report
|
|
24
|
-
- Rollback verification log
|
|
25
|
-
- Publish dry-run output
|
|
26
|
-
- Integrity and provenance manifest
|
|
27
|
-
|
|
28
|
-
## Fallback
|
|
1
|
+
# Distribution Skill Pack
|
|
2
|
+
|
|
3
|
+
Default tier: `expert`
|
|
4
|
+
|
|
5
|
+
## Purpose
|
|
6
|
+
Protect package installation and release distribution with transactional safety.
|
|
7
|
+
|
|
8
|
+
## In Scope
|
|
9
|
+
- Package validation
|
|
10
|
+
- Backup and rollback
|
|
11
|
+
- Compatibility checks
|
|
12
|
+
- Forbidden-file detection
|
|
13
|
+
- Publish hygiene and provenance
|
|
14
|
+
|
|
15
|
+
## Must-Have Checks
|
|
16
|
+
- Preflight validation before installation or publish
|
|
17
|
+
- Backup point before mutating user state
|
|
18
|
+
- Automatic rollback on failure
|
|
19
|
+
- Compatibility manifest present
|
|
20
|
+
- Evidence bundle attached to release
|
|
21
|
+
|
|
22
|
+
## Evidence
|
|
23
|
+
- Install validation report
|
|
24
|
+
- Rollback verification log
|
|
25
|
+
- Publish dry-run output
|
|
26
|
+
- Integrity and provenance manifest
|
|
27
|
+
|
|
28
|
+
## Fallback
|
|
29
29
|
- If automated rollback cannot be guaranteed, the operation must stop before mutation.
|
|
@@ -1,36 +1,36 @@
|
|
|
1
|
-
# Frontend Engineering Skills
|
|
2
|
-
|
|
3
|
-
The frontend domain covers component architecture, state management, performance optimization, accessibility, motion design, and visual polish. Content consolidated from **minimax-ai/skills** (design focus), **awesome-copilot** (architectural patterns), and **antigravity-awesome-skills** (React patterns), with production-grade automation and enforcement.
|
|
4
|
-
|
|
5
|
-
## Topics
|
|
6
|
-
- [UI Architecture](ui-architecture.md) - Smart/Dumb components, state management, composition patterns
|
|
7
|
-
- [Accessibility](accessibility.md) - WCAG compliance, keyboard navigation, semantic HTML, color contrast
|
|
8
|
-
- [Motion](motion.md) - Animation patterns, performance, CSS containment
|
|
9
|
-
- [Performance](performance.md) - Memoization, code splitting, bundle gates, profiling
|
|
10
|
-
|
|
11
|
-
## What Makes Ours Different
|
|
12
|
-
|
|
13
|
-
- Smart/Dumb Architecture (awesome-copilot) + animation system patterns (minimax) + React patterns (antigravity)
|
|
14
|
-
- Anti-Slop Enforcer (ABOVE LINE) - Detect forbidden visual patterns and style drift
|
|
15
|
-
- Accessibility Auditor (ABOVE LINE) - Detect contrast failures, ARIA issues, and keyboard navigation gaps
|
|
16
|
-
- Performance Budget Enforcer (ABOVE LINE) - Bundle size gates and LCP/FID/CLS thresholds
|
|
17
|
-
|
|
18
|
-
## Recommended Reading Order
|
|
19
|
-
|
|
20
|
-
1. `ui-architecture.md` - Mental models first (EXPERT)
|
|
21
|
-
2. `accessibility.md` - Compliance baseline (EXPERT)
|
|
22
|
-
3. `motion.md` - Design patterns and optimization (EXPERT)
|
|
23
|
-
4. `performance.md` - Profiling and gates (EXPERT)
|
|
24
|
-
|
|
25
|
-
## Coverage vs 3 Repos
|
|
26
|
-
|
|
27
|
-
| Aspect | antigravity | awesome-copilot | MiniMax | Ours |
|
|
28
|
-
|--------|-------------|-----------------|---------|------|
|
|
29
|
-
| Component Patterns | Medium | High | Medium | High + quality gates |
|
|
30
|
-
| Animation Patterns | Low | Low | High | High + performance rules |
|
|
31
|
-
| Accessibility | Medium | High | Medium | High + automated audits |
|
|
32
|
-
| Automation | None | None | None | Anti-slop, accessibility, and performance tooling |
|
|
33
|
-
|
|
34
|
-
## Default Tier Behavior
|
|
35
|
-
- Use `advance` for typical web apps (1500+ employees)
|
|
1
|
+
# Frontend Engineering Skills
|
|
2
|
+
|
|
3
|
+
The frontend domain covers component architecture, state management, performance optimization, accessibility, motion design, and visual polish. Content consolidated from **minimax-ai/skills** (design focus), **awesome-copilot** (architectural patterns), and **antigravity-awesome-skills** (React patterns), with production-grade automation and enforcement.
|
|
4
|
+
|
|
5
|
+
## Topics
|
|
6
|
+
- [UI Architecture](ui-architecture.md) - Smart/Dumb components, state management, composition patterns
|
|
7
|
+
- [Accessibility](accessibility.md) - WCAG compliance, keyboard navigation, semantic HTML, color contrast
|
|
8
|
+
- [Motion](motion.md) - Animation patterns, performance, CSS containment
|
|
9
|
+
- [Performance](performance.md) - Memoization, code splitting, bundle gates, profiling
|
|
10
|
+
|
|
11
|
+
## What Makes Ours Different
|
|
12
|
+
|
|
13
|
+
- Smart/Dumb Architecture (awesome-copilot) + animation system patterns (minimax) + React patterns (antigravity)
|
|
14
|
+
- Anti-Slop Enforcer (ABOVE LINE) - Detect forbidden visual patterns and style drift
|
|
15
|
+
- Accessibility Auditor (ABOVE LINE) - Detect contrast failures, ARIA issues, and keyboard navigation gaps
|
|
16
|
+
- Performance Budget Enforcer (ABOVE LINE) - Bundle size gates and LCP/FID/CLS thresholds
|
|
17
|
+
|
|
18
|
+
## Recommended Reading Order
|
|
19
|
+
|
|
20
|
+
1. `ui-architecture.md` - Mental models first (EXPERT)
|
|
21
|
+
2. `accessibility.md` - Compliance baseline (EXPERT)
|
|
22
|
+
3. `motion.md` - Design patterns and optimization (EXPERT)
|
|
23
|
+
4. `performance.md` - Profiling and gates (EXPERT)
|
|
24
|
+
|
|
25
|
+
## Coverage vs 3 Repos
|
|
26
|
+
|
|
27
|
+
| Aspect | antigravity | awesome-copilot | MiniMax | Ours |
|
|
28
|
+
|--------|-------------|-----------------|---------|------|
|
|
29
|
+
| Component Patterns | Medium | High | Medium | High + quality gates |
|
|
30
|
+
| Animation Patterns | Low | Low | High | High + performance rules |
|
|
31
|
+
| Accessibility | Medium | High | Medium | High + automated audits |
|
|
32
|
+
| Automation | None | None | None | Anti-slop, accessibility, and performance tooling |
|
|
33
|
+
|
|
34
|
+
## Default Tier Behavior
|
|
35
|
+
- Use `advance` for typical web apps (1500+ employees)
|
|
36
36
|
- Escalate to `expert` when component library, state complexity, or accessibility/performance tuning is critical
|