Update files
Seto Elkahfi committed
May 28, 2026 at 23:07 UTC
2d08bb138c118cb08421908585a81df0399d3430
4 files changed
+91
-65
.agents/skills/agent-client-protocol/SKILL.md
+6
-1
@@ -1,3 +1,8 @@
1
+---
2
+name: agent-client-protocol
3
+description: A JSON-RPC 2.0 protocol over stdio for integrating AI coding agents with editors.
4
+---
5
+
6
# Skill: Agent Client Protocol (ACP) — Rust Implementation
7
8
## Overview
@@ -311,4 +316,4 @@ Editor Agent
316
10. **Never write to stdout except JSON-RPC** — any library that prints to
317
stdout (`mistralrs` model metadata, stray `println!`, whatever) will
318
corrupt the wire. Redirect diagnostics to stderr. If a dependency writes
314
- to stdout internally, fix it or suppress it before shipping.
\ No newline at end of file
319
+ to stdout internally, fix it or suppress it before shipping.
.agents/skills/ai-assisted-coding/SKILL.md
+6
-1
@@ -1,3 +1,8 @@
1
+---
2
+name: ai-assisted-coding
3
+description: A skill for knowledge about AI-assisted coding, agents, harness, and everything in between.
4
+---
5
+
6
# Skill: AI-Assisted Coding Agents — Onde Inference Integration
7
8
## Overview
@@ -358,4 +363,4 @@ For sandboxed environments (iOS, tvOS, Android):
363
6. **Forgetting that `generate()` doesn't update history** — use it for
364
one-shot enhancements (prompt expansion, code review) that shouldn't pollute
365
the main conversation. Use `send_message()` / `stream_message()` for the
361
- primary turn loop.
\ No newline at end of file
366
+ primary turn loop.
.agents/skills/branding/SKILL.md
+73
-62
@@ -1,24 +1,33 @@
1
-# Skill: Branding and naming reference
1
+---
2
+name: branding
3
+description: Keep siGit Code naming, casing, and product voice consistent across docs, UI copy, release notes, and package metadata.
4
+allowed-tools: Read, Write, Edit, Glob, Grep, AskUserQuestion
5
+user-invocable: true
6
+---
7
+
8
+# Branding: siGit Code naming and voice
9
+
10
+Use this skill when you are writing docs, release notes, UI copy, package descriptions, setup guides, or anything else user-facing in this repo.
11
3
-## Overview
12
+The main job is simple: keep the names straight.
13
5
-Use this file when writing docs, release notes, UI copy, package metadata, or setup guides for this repository.
14
+## The name map
15
7
-The short version:
16
+These names are case-sensitive.
17
9
-- **Product / brand name:** `siGit Code`
18
+- **Product / brand:** `siGit Code`
19
- **CLI command:** `sigit`
20
- **Rust crate:** `sigit`
21
+- **Repository slug:** `getsigit/sigit`
22
- **npm package:** `@smbcloud/sigit`
23
- **PyPI package:** `sigit-code`
14
-- **Company name:** `smbCloud`
15
-- **LLM backend name:** `Onde Inference`
24
+- **Company:** `smbCloud`
25
+- **LLM backend in prose:** `Onde Inference`
26
+- **Rust crate for the backend:** `onde`
27
+- **Protocol acronym:** `ACP`
28
+- **Long form when needed:** `Agent Client Protocol (ACP)`
29
17
-The most common mistake is mixing the product name with the command name.
18
-
19
----
20
-
21
-## Primary rule
30
+## First rule
31
32
When you mean the product, write **`siGit Code`** exactly like that.
33
@@ -36,13 +45,18 @@ Wrong:
45
- `sigit Code`
46
- `SIGIT`
47
39
-Do not shorten the product name to just `siGit` in documentation or marketing copy unless there is a very specific reason and the surrounding text makes it unmistakable.
48
+Do not shorten the product name to just `siGit` in docs or marketing copy unless there is a very specific reason and the sentence still reads clearly.
49
41
----
50
+## Second rule
51
43
-## Use lowercase names for commands and packages
52
+When you mean something users type, install, import, or clone, use the literal lowercase name.
53
45
-Use lowercase `sigit` when you mean the executable, crate, repo slug, or package name.
54
+That means:
55
+
56
+- `sigit` for the command, crate, and repo slug
57
+- `@smbcloud/sigit` for npm
58
+- `sigit-code` for PyPI
59
+- `onde` for the Rust crate
60
61
Examples:
62
@@ -52,42 +66,36 @@ Examples:
66
- Install with `pip install sigit-code`.
67
- The repository is `getsigit/sigit`.
68
55
-This distinction matters:
56
-
57
-- **Brand / product:** `siGit Code`
58
-- **Command / package / repo:** `sigit`
69
+A good gut-check:
70
60
----
71
+> If this is the thing a user types or installs, keep the literal package or command name.
72
+> If this is the thing you are describing, use the branded product name.
73
62
-## Recommended wording patterns
74
+## Preferred wording
75
64
-### Product description
76
+Keep the prose plain and direct.
77
78
Prefer:
79
80
- `siGit Code is a local coding agent.`
81
- `siGit Code runs on your machine.`
82
- `siGit Code works with any codebase.`
83
+- `Install siGit Code with Cargo:`
84
+- `To start siGit Code, run `sigit`.`
85
86
Avoid:
87
88
- `siGit is a local coding agent.`
89
- `sigit is a coding assistant.`
90
- `The siGit product...`
91
+- inflated marketing language that makes the copy sound generic
92
78
-### Install instructions
79
-
80
-Prefer:
81
-
82
-- `Install siGit Code with Cargo:`
83
-- `Install siGit Code from npm:`
84
-- To start siGit Code, run `sigit`.
85
-
86
-That keeps the brand name in prose and the command name in code.
93
+If a sentence feels awkward because of the brand name, rewrite the sentence. Do not change the name.
94
88
-### Editor setup
95
+## Editor setup rules
96
90
-In UI-facing examples, keep the displayed agent name as `siGit Code`.
97
+In UI-facing examples, the visible label should stay `siGit Code`.
98
+The executable should stay `sigit`.
99
100
Example:
101
@@ -102,19 +110,13 @@ Example:
110
}
111
```
112
105
-The visible name is `siGit Code`. The executable path is `sigit`.
106
-
107
----
113
+The same rule applies in VS Code ACP examples, screenshots, panel labels, and release notes.
114
109
-## Other names that should stay consistent
115
+## Other names that must stay exact
116
117
### smbCloud
118
113
-Always write `smbCloud` with a lowercase `smb` and uppercase `C`.
114
-
115
-Correct:
116
-
117
-- `smbCloud`
119
+Always write `smbCloud` with lowercase `smb` and uppercase `C`.
120
121
Wrong:
122
@@ -124,36 +126,45 @@ Wrong:
126
127
### Onde Inference
128
127
-Use `Onde Inference` when referring to the product or project.
128
-
129
-Use `onde` when referring to the Rust crate.
129
+Use `Onde Inference` when you mean the product or project.
130
+Use `onde` when you mean the Rust crate.
131
132
Examples:
133
134
- `siGit Code uses Onde Inference as its local LLM backend.`
134
-- The Rust dependency is `onde`.
135
+- `The Rust dependency is `onde`.`
136
137
### ACP
138
138
-Use `ACP` for the protocol acronym.
139
+Use `ACP` for the acronym.
140
+Use `Agent Client Protocol (ACP)` on first mention when the long form helps.
141
140
-Preferred long form:
142
+## Humanizing without breaking branding
143
142
-- `Agent Client Protocol (ACP)` on first mention when useful
144
+If you are also cleaning up AI-ish writing, preserve every case-sensitive name exactly as written.
145
144
----
146
+That includes:
147
146
-## Copy checklist
148
+- `siGit Code`
149
+- `smbCloud`
150
+- `Onde Inference`
151
+- `ACP`
152
+- `sigit`
153
+- `@smbcloud/sigit`
154
+- `sigit-code`
155
+- `onde`
156
148
-Before you finish any docs or release-note edit, check these quickly:
157
+Do not "smooth out" a brand name. Do not re-case package names to make a sentence look nicer. Rewrite around them.
158
150
-1. Did you use `siGit Code` for the product name?
151
-2. Did you keep `sigit` lowercase for commands and package names?
152
-3. Did you keep `smbCloud` cased correctly?
153
-4. Did you keep `Onde Inference` cased correctly in prose?
154
-5. In setup examples, does the visible editor label say `siGit Code` while the command stays `sigit`?
159
+## Quick checklist
160
156
----
161
+Before you finish any doc or release-note edit, check these:
162
+
163
+1. Did you use `siGit Code` when referring to the product?
164
+2. Did you keep `sigit` lowercase for commands, crates, and repo references?
165
+3. Did you keep `@smbcloud/sigit` and `sigit-code` exact?
166
+4. Did you keep `smbCloud` and `Onde Inference` cased correctly?
167
+5. In setup examples, does the visible editor label say `siGit Code` while the command stays `sigit`?
168
169
## Fast replacements
170
@@ -165,9 +176,9 @@ Common fixes:
176
- `On macOS, siGit` -> `On macOS, siGit Code`
177
- `Sigit` -> usually `siGit Code` or `sigit`, depending on context
178
168
-When in doubt, ask:
179
+When in doubt, ask one question:
180
170
-> Am I talking about the branded product, or the literal command/package name?
181
+> Am I talking about the product, or the literal thing a user types?
182
183
If it is the product, use `siGit Code`.
173
-If it is something users type or install, use `sigit`.
184
+If it is the command or package, use the exact lowercase name.
.agents/skills/tool-calling/SKILL.md
+6
-1
@@ -1,3 +1,8 @@
1
+---
2
+name: tool-calling
3
+description: A skill for tool calling in siGit Code, supporting agentic tool execution with Qwen 3 models.
4
+---
5
+
6
# Skill: Tool Calling in siGit Code
7
8
## Overview
@@ -287,4 +292,4 @@ The `qwen3_8b()` constructor only exists in the local Onde SDK until it's pushed
292
| `sigit/src/setup.rs` | HF cache setup pointing to shared App Group container |
293
| `onde/src/inference/types.rs` | `ToolDefinition`, `ToolCallRequest`, `ToolResult`, `ToolAwareResult` |
294
| `onde/src/inference/engine.rs` | `send_message_with_tools()`, `send_tool_results()`, `attach_tools()`, `parse_tool_calls()`, `replay_history_with_tools()`, `GgufModelConfig::qwen3_8b()` |
290
-| `onde/src/inference/models.rs` | Model constants and `SUPPORTED_MODELS` array |
\ No newline at end of file
295
+| `onde/src/inference/models.rs` | Model constants and `SUPPORTED_MODELS` array |