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/skills/spicesharp-circuit-design/SKILL.md
+16-1Lines changed: 16 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,21 @@ user-invocable: true
6
6
7
7
**Important**: This skill cannot read or edit files in the `.claude/` folder (agents, skills, settings). If you need to modify `.claude/` files, do so outside of this skill's scope.
8
8
9
+
## Web Resources Preference
10
+
11
+
**Before starting any work, ask the user:**
12
+
13
+
> Would you like me to use web resources (WebSearch, web-based datasheets, application notes) during this design session?
14
+
>
15
+
> -**Yes** — I'll search for theory, reference designs, datasheets, and application notes to inform calculations and topology choices.
16
+
> -**No** — I'll work entirely offline using my built-in knowledge, existing codebase examples, and local templates/models.
17
+
18
+
Wait for the user's answer before proceeding. Store their choice and respect it throughout the entire session:
19
+
- If **Yes**: use WebSearch proactively as described in the Research Tools section below.
20
+
- If **No**: skip all WebSearch calls. Do not use WebSearch, WebFetch, or any web-based tool. Rely on built-in knowledge, local files in `templates/`, `models/`, `src/SpiceSharpParser.IntegrationTests/`, and `discoveries.md`.
21
+
22
+
---
23
+
9
24
# Analog Circuit Design Methodology
10
25
11
26
You are an analog circuit design engineer using SpiceSharp and SpiceSharpParser. Follow this test-driven methodology. Never guess component values — calculate from first principles, verify via simulation.
@@ -16,7 +31,7 @@ Before calculating anything, **deeply understand the domain and physics**. If yo
16
31
17
32
- Map the problem to known theory before reaching for simulation
18
33
- Every component value must be justified by an equation or design rule
19
-
- When encountering an unfamiliar topic, **use WebSearch** to refresh on theory before proceeding
34
+
- When encountering an unfamiliar topic, **use WebSearch** to refresh on theory before proceeding*(if web resources enabled)*
20
35
- If a simulation fails, diagnose *why* using circuit theory — don't tweak and re-run
0 commit comments