@laitszkin/apollo-toolkit 3.11.8 → 3.12.0
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/CHANGELOG.md +15 -0
- package/align-project-documents/SKILL.md +20 -69
- package/align-project-documents/references/templates/standardized-docs-template.md +1 -1
- package/analyse-app-logs/scripts/__pycache__/filter_logs_by_time.cpython-312.pyc +0 -0
- package/analyse-app-logs/scripts/__pycache__/log_cli_utils.cpython-312.pyc +0 -0
- package/analyse-app-logs/scripts/__pycache__/search_logs.cpython-312.pyc +0 -0
- package/archive-specs/SKILL.md +18 -70
- package/commit-and-push/SKILL.md +24 -52
- package/develop-new-features/SKILL.md +15 -60
- package/discover-edge-cases/SKILL.md +16 -75
- package/discover-security-issues/SKILL.md +49 -83
- package/docs-to-voice/scripts/__pycache__/docs_to_voice.cpython-312.pyc +0 -0
- package/enhance-existing-features/SKILL.md +36 -57
- package/generate-spec/SKILL.md +14 -14
- package/generate-spec/references/templates/coordination.md +0 -1
- package/generate-spec/scripts/__pycache__/create-specscpython-312.pyc +0 -0
- package/implement-specs/SKILL.md +27 -62
- package/implement-specs-with-subagents/SKILL.md +28 -71
- package/implement-specs-with-worktree/SKILL.md +38 -62
- package/init-project-html/SKILL.md +27 -115
- package/katex/scripts/__pycache__/render_katex.cpython-312.pyc +0 -0
- package/maintain-project-constraints/SKILL.md +24 -78
- package/maintain-project-constraints/references/constraint-file-reference.md +58 -0
- package/merge-changes-from-local-branches/SKILL.md +36 -99
- package/open-github-issue/scripts/__pycache__/open_github_issue.cpython-312.pyc +0 -0
- package/optimise-skill/SKILL.md +1 -1
- package/optimise-skill/references/definition.md +5 -5
- package/optimise-skill/references/example_skill.md +1 -1
- package/package.json +1 -1
- package/read-github-issue/scripts/__pycache__/find_issues.cpython-312.pyc +0 -0
- package/read-github-issue/scripts/__pycache__/read_issue.cpython-312.pyc +0 -0
- package/resolve-review-comments/scripts/__pycache__/review_threads.cpython-312.pyc +0 -0
- package/review-change-set/SKILL.md +41 -91
- package/review-codebases/SKILL.md +42 -99
- package/review-spec-related-changes/SKILL.md +42 -77
- package/solve-issues-found-during-review/SKILL.md +38 -66
- package/spec-to-project-html/SKILL.md +27 -76
- package/submission-readiness-check/SKILL.md +35 -55
- package/systematic-debug/SKILL.md +37 -53
- package/test-case-strategy/SKILL.md +38 -85
- package/text-to-short-video/scripts/__pycache__/enforce_video_aspect_ratio.cpython-312.pyc +0 -0
- package/update-project-html/SKILL.md +25 -94
- package/version-release/SKILL.md +39 -74
- package/archive-specs/references/templates/architecture.md +0 -21
- package/archive-specs/references/templates/docs-index.md +0 -39
- package/archive-specs/references/templates/features.md +0 -25
- package/archive-specs/references/templates/principles.md +0 -28
|
@@ -1,25 +0,0 @@
|
|
|
1
|
-
# <功能類別名稱>
|
|
2
|
-
|
|
3
|
-
[One-sentence summary of this functional category from a user perspective.]
|
|
4
|
-
|
|
5
|
-
## <功能名稱>
|
|
6
|
-
|
|
7
|
-
- **Given** <前置條件>
|
|
8
|
-
- **When** <使用者操作>
|
|
9
|
-
- **Then** <預期結果>
|
|
10
|
-
|
|
11
|
-
## <功能名稱>
|
|
12
|
-
|
|
13
|
-
- **Given** <前置條件>
|
|
14
|
-
- **When** <使用者操作>
|
|
15
|
-
- **Then** <預期結果>
|
|
16
|
-
|
|
17
|
-
---
|
|
18
|
-
|
|
19
|
-
## Writing Rules
|
|
20
|
-
|
|
21
|
-
- Describe behavior from a user's perspective; never mention file paths, function names, or database tables.
|
|
22
|
-
- Use BDD phrasing: **Given** (precondition) → **When** (action) → **Then** (outcome).
|
|
23
|
-
- Each file covers exactly one functional category (e.g., authentication, data export, notifications).
|
|
24
|
-
- Group related features under descriptive subheadings.
|
|
25
|
-
- Title the file with a term users would recognize, not a module name.
|
|
@@ -1,28 +0,0 @@
|
|
|
1
|
-
# <慣例類別>
|
|
2
|
-
|
|
3
|
-
[One-sentence summary of what this convention area covers.]
|
|
4
|
-
|
|
5
|
-
## <慣例名稱>
|
|
6
|
-
|
|
7
|
-
<慣例描述>
|
|
8
|
-
|
|
9
|
-
**理由**: <為什麼採用此慣例>
|
|
10
|
-
|
|
11
|
-
**範例**: <從代碼庫提取的具體範例>
|
|
12
|
-
|
|
13
|
-
## <慣例名稱>
|
|
14
|
-
|
|
15
|
-
<慣例描述>
|
|
16
|
-
|
|
17
|
-
**理由**: <為什麼採用此慣例>
|
|
18
|
-
|
|
19
|
-
**範例**: <從代碼庫提取的具體範例>
|
|
20
|
-
|
|
21
|
-
---
|
|
22
|
-
|
|
23
|
-
## Writing Rules
|
|
24
|
-
|
|
25
|
-
- Each file covers one convention area (e.g., naming, coding style, dependency management, error handling, testing).
|
|
26
|
-
- State the convention clearly.
|
|
27
|
-
- Provide rationale traceable to the codebase.
|
|
28
|
-
- Include a brief example from the codebase, not an invented one.
|