开发编程
#writing
code-quality
General Correctness rules, Rust patterns, comments, avoiding over-engineering. When writing code always take these into account
DeepseekModel
官方收录技能
质量 优秀 · 90
v1.0.0
获取
https://deepseekmodel.com/api/download.php?id=tursodatabase-turso-claude-skills-code-quality-skill-md&format=skill
下载 .skill
标准格式，含 system_prompt 与 model_config，导入任意 Agent 框架即可使用
.skill 文件中 system_prompt 字段的实际内容。
name code-quality description General Correctness rules, Rust patterns, comments, avoiding over-engineering. When writing code always take these into account Code Quality Guide Core Principle Production database. Correctness paramount. Crash > corrupt. Correctness Rules No workarounds or quick hacks. Handle all errors, check invariants Assert often. Never silently fail or swallow edge cases Crash on invalid state if it risks data integrity. Don't continue in undefined state Consider edge cases. On long enough timeline, all possible bugs will happen Rust Patterns Make illegal states unrepresentable Exhaustive pattern matching Prefer enums over strings/sentinels Minimize heap allocations Write CPU-friendly code (microsecond = long time) If-Statements Wrong: if condition { // happy path } else { // "shouldn't happen" - silently ignored } Right: // If only one branch should ever be hit: assert! (condition, "invariant violated: ..." ); // OR return Err (LimboError:: InternalError ( "unexpected state" . into ())); // OR unreachable! ( "impossible state: ..." ); Use if-statements only when both branches are expected paths. Comments Do: Document WHY, not what Document functions, structs, enums, variants Focus on why something is necessary Don't: Comments that repeat code References to AI conversations ("This test should trigger the bug") Temporal markers ("added", "existing code", "Phase 1") Avoid Over-Engineering Only changes directly requested or clearly necessary Don't add features beyond what's asked Don't add docstrings/comments to unchanged code Don't add error handling for impossible scenarios Don't create abstractions for one-time operations Three similar lines > premature abstraction Index Mutations When code involves index inserts, deletes, or conflict resolution, double-check the ordering against SQLite. Wrong ordering causes index inconsistencies. and easy to miss. Ensure understanding of IO model Async IO model Cleanup Delete unused code completely No backwards-compat hacks (renamed _vars , re-exports, // removed comments)
Agent 识别该技能的关键词，点击任意一个即可复制。
该技能未提供触发词。
下载的 .skill 包内含以下字段。
| 字段 | 说明 |
|---|---|
| format | 格式标识（skill/v1） |
| skill_id | 技能唯一 ID |
| name | 技能名称 |
| version | 版本号 |
| description | 技能描述 |
| category | 所属分类（数组） |
| trigger_words | 触发词列表 |
| tags | 标签列表 |
| source | 来源标识 |
| source_url | 来源链接（本页地址） |
| exported_at | 导出时间（每次下载生成） |
| system_prompt | 系统提示词正文 |
| model_config | 模型参数：provider / model / temperature / max_tokens / top_p |
| examples | 示例 |
| install_guide | 各平台导入说明（Coze / Dify / Claude / 自定义框架） |
