-
Notifications
You must be signed in to change notification settings - Fork 16
Add Claude Code skill for RFD research #362
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
Open
plaidfinch
wants to merge
7
commits into
main
Choose a base branch
from
claude-code-rfd-skill
base: main
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.
Open
Conversation
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
Adds a Claude Code skill that enables AI-assisted research of Oxide RFDs. The skill provides read-only access to search, view, and analyze RFDs using rfd-cli. Features: - First-time setup walkthrough (install, configure, authenticate) - All read-only CLI commands with correct syntax - 53 curated foundational RFDs organized by category - Guidance on following links and cross-references - Research strategies for simple lookups vs comprehensive research 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
bdb6f5a to
55ca3e4
Compare
🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Update the rfd-api skill to encourage more liberal quoting from RFD content when answering questions. This makes answers more authoritative and helps users understand the source material better. Changes: - Add new guideline #5 encouraging direct quotes from RFDs - Emphasize quoting technical decisions, rationale, and determinations - Update guideline #6 to supplement summaries with direct quotes Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Add a new "Writing Style: Learning from Oxide RFDs" section that captures the distinctive characteristics of Oxide's engineering writing: Core Principles: - Honest about tradeoffs (acknowledge what wasn't chosen) - Pragmatic over perfect (operational viability beats theoretical purity) - Philosophical grounding (Goals/Non-Goals, the "why" before "how") - Determinations matter (actual decisions after exploration) - Security realism, not theater (honest about remaining attack vectors) - Acknowledge uncertainty (open questions, future work) - Show evolution of thinking (what was tried, what changed) - User impact focus (customer sovereignty, operational concerns) Stylistic Elements: - Conversational yet precise (rhetorical questions, analogies) - Memorable phrases (quotable insights) - Explicit structure (numbered lists, clear tradeoffs) - Technical depth with context (the "why" behind choices) This guidance helps maintain the authentic voice and intellectual honesty that makes RFDs valuable engineering documents. Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Refine writing guidance to clarify that the goal is to educate through coherent narrative, not to compile disconnected quotes. Key changes: - Add "Overall Approach: Narrative, Not Vignettes" section up front - Emphasize the WHY, HOW, and WHAT NEXT structure - "Use quotes to illuminate, not to replace narrative" - Explicitly warn against "vignetted quotes" - Quotes should support and illuminate the explanation - Goal is fluid, conversational, educational writing Updated both the Usage Guidelines and Writing Style sections to reinforce this principle consistently. Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Refine writing guidance to avoid promotional language and formulaic
structure:
Tone and Audience:
- Write for technical peers (Oxide employees, skilled professionals)
- Avoid superlatives and praise ("elegant", "beautiful", "novel")
- No need to convince readers Oxide is impressive
- Conversational, not formulaic (no repeated "Why this mattered" sections)
- Vary language naturally, weave implications into narrative flow
- Show, don't evaluate - let the design speak for itself
The audience knows why Oxide is unique and wants to understand
the architecture, not be sold on it.
Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds a Claude Code skill that enables AI-assisted research of Oxide RFDs. The skill provides read-only access to search, view, and analyze RFDs using rfd-cli.
Features:
Call for improvement: the curated RFDs were collected by a comprehensive summarizing search by Claude; please improve this list, either by pruning or expanding!