You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CLAUDE.md
+30Lines changed: 30 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,6 +13,36 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
13
13
- Instruct your subagents to use their respective task plans to complete the tasks from the plans directory if they are available.
14
14
- Instead of assuming bun commands look up the bun documentation: https://bun.sh/docs/cli/(run, init, add, update, publish, etc.), https://bun.sh/docs/api/(http, fetch, etc.) and https://bun.sh/docs/bundler
15
15
16
+
## Development Process for New Features
17
+
18
+
When developing a new feature, follow this test-driven development approach:
19
+
20
+
1.**Plan and Research Phase**
21
+
- Create a rough plan and concept for the feature
22
+
- Think deeply about the implementation approach
23
+
- Use web search extensively to research:
24
+
- Appropriate libraries to use
25
+
- Best practices for the feature domain
26
+
- API documentation for chosen libraries
27
+
- Similar implementations for reference
28
+
- Document your findings and decisions
29
+
30
+
2.**Test Implementation Phase**
31
+
- Write thorough unit and integration tests FIRST based on:
32
+
- The API documentation of chosen libraries
33
+
- Expected behavior of the feature
34
+
- Edge cases and error scenarios
35
+
- Ensure tests are comprehensive and cover all planned functionality
36
+
- Tests should be written to match our existing test suite patterns
37
+
38
+
3.**Feature Implementation Phase**
39
+
- Only after tests are complete, start writing the actual implementation
40
+
- Write code to satisfy the tests you've created
41
+
- Let the tests guide your implementation
42
+
-**Never write software first and then tests later**
43
+
44
+
This test-driven approach ensures better design, more reliable code, and easier maintenance.
45
+
16
46
## Project Overview
17
47
18
48
This is an MCP server implementation that provides access to Rust crate documentation via the docs.rs JSON API. The project enables AI assistants to fetch and parse Rust documentation, making it easier to provide accurate information about Rust crates, their APIs, and usage. The server includes intelligent caching and supports fetching documentation for specific crate versions and items.
0 commit comments