-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Add Claude Skills #6338
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
dangell7
wants to merge
3
commits into
develop
Choose a base branch
from
dangell7/add-claude
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+4,241
−2
Draft
Add Claude Skills #6338
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,54 @@ | ||
| # Workflow Orchestration | ||
|
|
||
| ## 1. Plan Mode Default | ||
| - Enter plan mode for ANY non-trivial task (3+ steps or architectural decisions) | ||
| - If something goes sideways, STOP and re-plan immediately - don't keep pushing | ||
| - Use plan mode for verification steps, not just building | ||
| - Write detailed specs upfront to reduce ambiguity | ||
|
|
||
| ## 2. Subagent Strategy | ||
| - Use subagents liberally to keep main context window clean | ||
| - Offload research, exploration, and parallel analysis to subagents | ||
| - For complex problems, throw compute at it via parallelizing | ||
| - One task per subagent for focused execution | ||
|
|
||
| ## 3. Self-Improvement Loop | ||
| - After ANY correction from the user: update `tasks/lessons.md` with the pattern | ||
| - Write rules for yourself that prevent the same mistake | ||
| - Ruthlessly iterate on these rules until mistake drops | ||
| - Review lessons at session start for relevant project | ||
|
|
||
| ## 4. Verification Before Done | ||
| - Never mark a task complete without proving it works | ||
| - Diff behavior between main and your changes when relevant | ||
| - Ask yourself: "Would a staff engineer approve this?" | ||
| - Run tests, check logs, demonstrate correctness | ||
|
|
||
| ## 5. Demand Elegance (Balanced) | ||
| - For non-trivial changes: pause and ask "is there a more elegant way?" | ||
| - If a fix feels hacky: "Know now, do later, implement the elegant solution" | ||
| - Skip this for simple, obvious fixes - don't over-engineer | ||
| - Challenge your own first solution | ||
|
|
||
| ## 6. Autonomous Bug Fixing | ||
| - When given a bug report: just fix it. Don't ask for hand-holding | ||
| - Point at logs, errors, failing tests - then resolve them | ||
| - Zero context switching required from the user | ||
| - Go fix failing CI tests without being told how | ||
|
|
||
| # Task Management | ||
|
|
||
| 1. **Plan First**: Write plan to `tasks/todo.md` with checkable items | ||
| 2. **Verify Plans**: Check in before starting implementation | ||
| 3. **Track Progress**: Mark items complete as you go | ||
| 4. **Explain Changes**: High-level summary at each step | ||
| 5. **Document Results**: Add review section to `tasks/todo.md` | ||
| 6. **Capture Lessons**: Update `tasks/lessons.md` after corrections | ||
|
|
||
| # Core Principles | ||
|
|
||
| **Simplicity First**: Make every change as simple as possible. Impact minimal code. | ||
|
|
||
| **No Boilerplate**: Skip documentation. No README/docs bloat. Test only if requested. | ||
|
|
||
| **Minimal Impact**: Changes should only touch what's necessary. Avoid introducing bugs. | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might be a good addition.