開発
#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)
このスキルを起動するキーワード。クリックでコピーできます。
このスキルにはトリガーワードがありません。
ダウンロードした .skill に含まれるフィールド。
| フィールド | 説明 |
|---|---|
| format | フォーマット識別子（skill/v1） |
| skill_id | スキル固有 ID |
| name | スキル名 |
| version | バージョン |
| description | 説明 |
| category | カテゴリ（配列） |
| trigger_words | トリガーワード |
| tags | タグ |
| source | ソース |
| source_url | ソース URL（本ページ） |
| exported_at | エクスポート日時（ダウンロード毎） |
| system_prompt | システムプロンプト本文 |
| model_config | モデル設定：provider / model / temperature / max_tokens / top_p |
| examples | サンプル |
| install_guide | 各プラットフォームの導入説明（Coze / Dify / Claude / カスタム） |
