[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KNE69ZGR3GSQHSPBK7D3Z9":3,"skill-same:01M6KNE69ZGR3GSQHSPBK7D3Z9":69},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":6,"updatedAt":54,"install":55,"resources":68},"01M6KNE69ZGR3GSQHSPBK7D3Z9","speckit-sync-backfill",null,"Generate a new spec from unspecced code feature (backfill)","AI-native-Systems-Research\u002Fai-native-storage-certus","AI-native-Systems-Research","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F270755458?v=4","01M6KKQWSJX0D4X33E0KKSR4WM","AI-native Systems Research","01M6KKQWXTKR6MYVQMPKVJ5WD5",3,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus\u002Fblob\u002Funstable\u002Fcomponents\u002Feviction-policy-session-lists\u002F.claude\u002Fskills\u002Fspeckit-sync-backfill\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"speckit sync backfill","backfill","sync","speckit","project","new","kit","with","spec-kit","feature","commands","directory","structure","specify","code","generate","project structure","github","spec","2026-11-10 10:12:30",false,"---\nname: speckit-sync-backfill\ndescription: Generate a new spec from unspecced code feature (backfill)\ncompatibility: Requires spec-kit project structure with .specify\u002F directory\nmetadata:\n  author: github-spec-kit\n  source: sync:commands\u002Fbackfill.md\n---\n\n# Spec Sync: Backfill Spec\n\nGenerate a complete spec from an existing, unspecced code feature. Extracts intent from implementation, tests, and documentation.\n\n## User Input\n\n$ARGUMENTS\n\nThe argument should be one of:\n- A feature name (e.g., \"reconciliation\", \"hints\")\n- A file path (e.g., \"src\u002FFina.Cli\u002FCommands\u002FRegister\u002FRegisterReconcileCommand.cs\")\n- An identifier from the drift report (e.g., \"unspecced-3\")\n\n## Context\n\nIf a feature name is provided, search for relevant files:\n- Commands with that name\n- Services with that name\n- Tests for that feature\n- Any existing documentation\n\n## Steps\n\n### 1. Discover Feature Scope\n\nFind all files related to the feature:\n\n```bash\n# Commands\nfind src -name \"*[Feature]*Command.cs\" -o -name \"*[Feature]*.cs\"\n\n# Services\nfind src -name \"*[Feature]*Service.cs\"\n\n# Tests\nfind tests -name \"*[Feature]*Tests.cs\"\n\n# Docs\nfind docs -name \"*[feature]*\"\n```\n\n### 2. Analyze Implementation\n\nRead the discovered files and extract:\n\n**From Commands:**\n- Command name and description\n- Options and arguments\n- Validation rules\n- Error handling\n\n**From Services:**\n- Public methods (these become requirements)\n- Business logic rules\n- Dependencies on other services\n- Edge case handling\n\n**From Tests:**\n- Test scenarios (become acceptance scenarios)\n- Expected behaviors\n- Edge cases tested\n\n**From Existing Docs:**\n- Any informal documentation\n- README sections\n- Comments explaining \"why\"\n\n### 3. Infer User Stories\n\nFrom the command\u002Fservice analysis, generate user stories:\n\n```markdown\n### User Story 1 - [Primary Use Case] (Priority: P1)\n\nAs a user, I want to [action from main command]\nso that [benefit inferred from feature purpose].\n\n**Acceptance Scenarios**:\n\n1. **Given** [precondition from tests], **When** [action], **Then** [expected result].\n```\n\n### 4. Extract Requirements\n\nConvert implementation behaviors to requirements:\n\n**From method signatures:**\n```csharp\npublic async Task\u003CReconcileResult> ReconcileAsync(string profileName, ...)\n```\n→ `FR-001: System MUST support reconciliation per profile.`\n\n**From validation:**\n```csharp\nif (!_authService.IsAuthenticated) throw ...\n```\n→ `FR-002: System MUST validate authentication before reconciliation.`\n\n**From business logic:**\n```csharp\nvar matches = _fuzzyMatcher.FindMatches(transactions, registryRows, threshold: 0.85);\n```\n→ `FR-003: System MUST use fuzzy matching with configurable threshold to match transactions.`\n\n### 5. Generate Spec Structure\n\nFollow the standard spec template:\n\n```markdown\n# Feature Specification: [Feature Name]\n\n**Feature Branch**: `[spec-id]`\n**Created**: [today's date]\n**Status**: Backfilled\n**Source**: Generated from existing implementation\n\n## Backfill Notice\n\n> ⚠️ This spec was generated from existing code via `speckit.sync.backfill`.\n> It documents current behavior, not original intent.\n> Review carefully and update to reflect desired behavior.\n\n## User Scenarios & Testing\n\n### User Story 1 - [Story] (Priority: P1)\n[generated user story]\n\n## Requirements\n\n### Functional Requirements\n\n- **FR-001**: [extracted requirement]\n- **FR-002**: [extracted requirement]\n\n### CLI Commands\n\n- **FR-0XX**: System MUST provide `fina [command]` command...\n\n## Key Entities\n\n- **[Entity]**: [description from code]\n\n## Dependencies\n\n- **Spec [XXX]**: [dependency identified from imports\u002Fservices]\n\n## Success Criteria\n\n- **SC-001**: [derived from tests or obvious metrics]\n\n## Implementation Notes\n\n> These notes capture current implementation details that may or may not\n> belong in the spec long-term.\n\n- [implementation detail 1]\n- [implementation detail 2]\n```\n\n### 6. Determine Spec ID\n\nFind the next available spec number:\n\n```bash\nls specs\u002F | grep -E '^[0-9]+' | sort -n | tail -1\n```\n\nSuggest: `{next_number}-{feature-name}`\n\n### 7. Generate Plan\n\nCreate `plan.md` documenting the implementation architecture:\n\n```markdown\n# Implementation Plan: [Feature Name]\n\n**Branch**: `[spec-id]` | **Date**: [today] | **Spec**: [spec.md](spec.md)\n**Context**: Backfilled from existing implementation. Documents current architecture.\n\n## Summary\n\n[Brief description of what the feature does]\n\n## Technical Context\n\n**Language\u002FVersion**: [detected from project]\n**Primary Dependencies**:\n- [Service 1] — [purpose]\n- [Service 2] — [purpose]\n\n**Performance Goals**: [if identifiable from code\u002Ftests]\n\n## Architecture\n\n### Service Layer\n\n```\n[Main Service]\n├── [Dependency 1]\n├── [Dependency 2]\n└── [Dependency 3]\n```\n\n### Flow\n\n1. [Step 1]\n2. [Step 2]\n3. [Step 3]\n\n### Key Design Decisions\n\n1. **[Decision 1]**: [rationale from code\u002Fcomments]\n2. **[Decision 2]**: [rationale]\n\n## Project Structure\n\n```text\nsrc\u002F[paths discovered]\ntests\u002F[paths discovered]\n```\n\n## Dependencies\n\n- **Spec [XXX]**: [dependency]\n\n## Testing\n\n[Test file locations]\n\n## Future Considerations\n\n[Any TODOs or comments suggesting future work]\n```\n\n### 8. Generate Quickstart\n\nFor user-facing features (CLI commands), create `quickstart.md`:\n\n```markdown\n# Quickstart: [Feature Name]\n\n[One-line description of what users can do]\n\n## Prerequisites\n\n1. [Prerequisite 1]\n2. [Prerequisite 2]\n\n## Basic Usage\n\n```bash\n# [Primary use case]\nfina [command] [args]\n```\n\n## Options\n\n| Option | Description |\n|--------|-------------|\n| `--option1` | [description] |\n| `--option2` | [description] |\n\n## Examples\n\n### [Use case 1]\n```bash\nfina [command] [example]\n```\n\n### [Use case 2]\n```bash\nfina [command] [example]\n```\n\n## Tips\n\n- [Tip 1]\n- [Tip 2]\n```\n\nSkip `quickstart.md` for internal\u002Fnon-user-facing features.\n\n### 9. Output Options\n\n**Preview Mode (default):**\nDisplay generated spec, plan, quickstart, and tasks for review.\n\n**Create Mode (`--create`):**\n1. Create `specs\u002F{id}\u002Fspec.md`\n2. Create `specs\u002F{id}\u002Fplan.md`\n3. Create `specs\u002F{id}\u002Fquickstart.md` (if user-facing)\n4. Create `specs\u002F{id}\u002Ftasks.md` (with review task)\n5. Report location\n\n### 10. Generate Review Task\n\nAdd a task to review the backfilled spec:\n\n```markdown\n# Tasks\n\n## Review Backfilled Spec\n\n- [ ] Review generated user stories for accuracy\n- [ ] Verify requirements match intended behavior (not just current behavior)\n- [ ] Remove implementation notes that don't belong in spec\n- [ ] Add any missing requirements\n- [ ] Mark spec status as \"Draft\" or \"Approved\"\n```\n\n## Example Usage\n\n```\n\u002Fspeckit.sync.backfill reconciliation\n\n\u002Fspeckit.sync.backfill src\u002FFina.App\u002FServices\u002FReconciliation\u002FReconciliationService.cs\n\n\u002Fspeckit.sync.backfill reconciliation --create\n\n\u002Fspeckit.sync.backfill hints --spec-id 014\n```\n\n## Notes\n\n- Backfilled specs should always be reviewed by a human\n- The spec documents current behavior, which may include bugs\n- Use this as a starting point, not a final spec\n- Consider whether the feature should be split into multiple specs\n- `plan.md` documents architecture decisions; useful for onboarding and future changes\n- `quickstart.md` is user documentation; skip for internal-only features","# Spec Sync: Backfill Spec\n\nGenerate a complete spec from an existing, unspecced code feature. Extracts intent from implementation, tests, and documentation.\n\n## User Input\n\n$ARGUMENTS\n\nThe argument should be one of:\n- A feature name (e.g., \"reconciliation\", \"hints\")\n- A file path (e.g., \"src\u002FFina.Cli\u002FCommands\u002FRegister\u002FRegisterReconcileCommand.cs\")\n- An identifier from the drift report (e.g., \"unspecced-3\")\n\n## Context\n\nIf a feature name is provided, search for relevant files:\n- Commands with that name\n- Services with that name\n- Tests for that feature\n- Any existing documentation\n\n## Steps\n\n### 1. Discover Feature Scope\n\nFind all files related to the feature:\n\n```bash\n# Commands\nfind src -name \"*[Feature]*Command.cs\" -o -name \"*[Feature]*.cs\"\n\n# Services\nfind src -name \"*[Feature]*Service.cs\"\n\n# Tests\nfind tests -name \"*[Feature]*Tests.cs\"\n\n# Docs\nfind docs -name \"*[feature]*\"\n```\n\n### 2. Analyze Implementation\n\nRead the discovered files and extract:\n\n**From Commands:**\n- Command name and description\n- Options and arguments\n- Validation rules\n- Error handling\n\n**From Services:**\n- Public methods (these become requirements)\n- Business logic rules\n- Dependencies on other services\n- Edge case handling\n\n**From Tests:**\n- Test scenarios (become acceptance scenarios)\n- Expected behaviors\n- Edge cases tested\n\n**From Existing Docs:**\n- Any informal documentation\n- README sections\n- Comments explaining \"why\"\n\n### 3. Infer User Stories\n\nFrom the command\u002Fservice analysis, generate user stories:\n\n```markdown\n### User Story 1 - [Primary Use Case] (Priority: P1)\n\nAs a user, I want to [action from main command]\nso that [benefit inferred from feature purpose].\n\n**Acceptance Scenarios**:\n\n1. **Given** [precondition from tests], **When** [action], **Then** [expected result].\n```\n\n### 4. Extract Requirements\n\nConvert implementation behaviors to requirements:\n\n**From method signatures:**\n```csharp\npublic async Task\u003CReconcileResult> ReconcileAsync(string profileName, ...)\n```\n→ `FR-001: System MUST support reconciliation per profile.`\n\n**From validation:**\n```csharp\nif (!_authService.IsAuthenticated) throw ...\n```\n→ `FR-002: System MUST validate authentication before reconciliation.`\n\n**From business logic:**\n```csharp\nvar matches = _fuzzyMatcher.FindMatches(transactions, registryRows, threshold: 0.85);\n```\n→ `FR-003: System MUST use fuzzy matching with configurable threshold to match transactions.`\n\n### 5. Generate Spec Structure\n\nFollow the standard spec template:\n\n```markdown\n# Feature Specification: [Feature Name]\n\n**Feature Branch**: `[spec-id]`\n**Created**: [today's date]\n**Status**: Backfilled\n**Source**: Generated from existing implementation\n\n## Backfill Notice\n\n> ⚠️ This spec was generated from existing code via `speckit.sync.backfill`.\n> It documents current behavior, not original intent.\n> Review carefully and update to reflect desired behavior.\n\n## User Scenarios & Testing\n\n### User Story 1 - [Story] (Priority: P1)\n[generated user story]\n\n## Requirements\n\n### Functional Requirements\n\n- **FR-001**: [extracted requirement]\n- **FR-002**: [extracted requirement]\n\n### CLI Commands\n\n- **FR-0XX**: System MUST provide `fina [command]` command...\n\n## Key Entities\n\n- **[Entity]**: [description from code]\n\n## Dependencies\n\n- **Spec [XXX]**: [dependency identified from imports\u002Fservices]\n\n## Success Criteria\n\n- **SC-001**: [derived from tests or obvious metrics]\n\n## Implementation Notes\n\n> These notes capture current implementation details that may or may not\n> belong in the spec long-term.\n\n- [implementation detail 1]\n- [implementation detail 2]\n```\n\n### 6. Determine Spec ID\n\nFind the next available spec number:\n\n```bash\nls specs\u002F | grep -E '^[0-9]+' | sort -n | tail -1\n```\n\nSuggest: `{next_number}-{feature-name}`\n\n### 7. Generate Plan\n\nCreate `plan.md` documenting the implementation architecture:\n\n```markdown\n# Implementation Plan: [Feature Name]\n\n**Branch**: `[spec-id]` | **Date**: [today] | **Spec**: [spec.md](spec.md)\n**Context**: Backfilled from existing implementation. Documents current architecture.\n\n## Summary\n\n[Brief description of what the feature does]\n\n## Technical Context\n\n**Language\u002FVersion**: [detected from project]\n**Primary Dependencies**:\n- [Service 1] — [purpose]\n- [Service 2] — [purpose]\n\n**Performance Goals**: [if identifiable from code\u002Ftests]\n\n## Architecture\n\n### Service Layer\n\n```\n[Main Service]\n├── [Dependency 1]\n├── [Dependency 2]\n└── [Dependency 3]\n```\n\n### Flow\n\n1. [Step 1]\n2. [Step 2]\n3. [Step 3]\n\n### Key Design Decisions\n\n1. **[Decision 1]**: [rationale from code\u002Fcomments]\n2. **[Decision 2]**: [rationale]\n\n## Project Structure\n\n```text\nsrc\u002F[paths discovered]\ntests\u002F[paths discovered]\n```\n\n## Dependencies\n\n- **Spec [XXX]**: [dependency]\n\n## Testing\n\n[Test file locations]\n\n## Future Considerations\n\n[Any TODOs or comments suggesting future work]\n```\n\n### 8. Generate Quickstart\n\nFor user-facing features (CLI commands), create `quickstart.md`:\n\n```markdown\n# Quickstart: [Feature Name]\n\n[One-line description of what users can do]\n\n## Prerequisites\n\n1. [Prerequisite 1]\n2. [Prerequisite 2]\n\n## Basic Usage\n\n```bash\n# [Primary use case]\nfina [command] [args]\n```\n\n## Options\n\n| Option | Description |\n|--------|-------------|\n| `--option1` | [description] |\n| `--option2` | [description] |\n\n## Examples\n\n### [Use case 1]\n```bash\nfina [command] [example]\n```\n\n### [Use case 2]\n```bash\nfina [command] [example]\n```\n\n## Tips\n\n- [Tip 1]\n- [Tip 2]\n```\n\nSkip `quickstart.md` for internal\u002Fnon-user-facing features.\n\n### 9. Output Options\n\n**Preview Mode (default):**\nDisplay generated spec, plan, quickstart, and tasks for review.\n\n**Create Mode (`--create`):**\n1. Create `specs\u002F{id}\u002Fspec.md`\n2. Create `specs\u002F{id}\u002Fplan.md`\n3. Create `specs\u002F{id}\u002Fquickstart.md` (if user-facing)\n4. Create `specs\u002F{id}\u002Ftasks.md` (with review task)\n5. Report location\n\n### 10. Generate Review Task\n\nAdd a task to review the backfilled spec:\n\n```markdown\n# Tasks\n\n## Review Backfilled Spec\n\n- [ ] Review generated user stories for accuracy\n- [ ] Verify requirements match intended behavior (not just current behavior)\n- [ ] Remove implementation notes that don't belong in spec\n- [ ] Add any missing requirements\n- [ ] Mark spec status as \"Draft\" or \"Approved\"\n```\n\n## Example Usage\n\n```\n\u002Fspeckit.sync.backfill reconciliation\n\n\u002Fspeckit.sync.backfill src\u002FFina.App\u002FServices\u002FReconciliation\u002FReconciliationService.cs\n\n\u002Fspeckit.sync.backfill reconciliation --create\n\n\u002Fspeckit.sync.backfill hints --spec-id 014\n```\n\n## Notes\n\n- Backfilled specs should always be reviewed by a human\n- The spec documents current behavior, which may include bugs\n- Use this as a starting point, not a final spec\n- Consider whether the feature should be split into multiple specs\n- `plan.md` documents architecture decisions; useful for onboarding and future changes\n- `quickstart.md` is user documentation; skip for internal-only features",{"name":5,"metadata":43,"description":7,"compatibility":46},{"author":44,"source":45},"github-spec-kit","sync:commands\u002Fbackfill.md","Requires spec-kit project structure with .specify\u002F directory","unstable","dc564aa356769b7754391c9fa4fdaa0f179f476c","components\u002Feviction-policy-session-lists\u002F.claude\u002Fskills\u002Fspeckit-sync-backfill",4,"https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus","https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research","https:\u002F\u002Fai-native-systems-research.github.io\u002Fai-native-systems-research\u002F","2026-11-12 06:08:32",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add AI-native-Systems-Research\u002Fai-native-storage-certus --skill speckit-sync-backfill",{"tool":61,"command":62},"bunx","bunx skills add AI-native-Systems-Research\u002Fai-native-storage-certus --skill speckit-sync-backfill",{"tool":64,"command":65},"pnpm","pnpm dlx skills add AI-native-Systems-Research\u002Fai-native-storage-certus --skill speckit-sync-backfill","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus\u002Fblob\u002Funstable\u002Fcomponents\u002Feviction-policy-session-lists\u002F.claude\u002Fskills\u002Fspeckit-sync-backfill\u002FSKILL.md",true,[],[70,86,101,112,127,139],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":38},"01M6KP29TWSNGADF3AJ47BR7TY","tools-spin-sync","Synchronize Spin\u002FPromela models with current source code and re-verify","https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus\u002Fblob\u002Funstable\u002Fcomponents\u002Fzyre\u002F.claude\u002Fskills\u002Ftools-spin-sync\u002FSKILL.md",[],[77,78,21,33,79,80,81,82,26,83,84,85],"tools spin sync","Tools","verify","model","models","name","re","source","source code",{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":38},"01M6KP277TDY3ZAJEBP5P6MDT8","tools-spin-model","Create a new Spin\u002FPromela formal verification model for a system property","https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus\u002Fblob\u002Funstable\u002Fcomponents\u002Fzyre\u002F.claude\u002Fskills\u002Ftools-spin-model\u002FSKILL.md",[],[93,80,78,94,95,96,97,98,24,99,100],"tools spin model","system","formal verification","number","for","prove","create","verification",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":38},"01M6KP250W406CEDSF02BRXT9D","tools-creusot-install","Install the Creusot Rust verification tool","https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus\u002Fblob\u002Funstable\u002Fcomponents\u002Fzyre\u002F.claude\u002Fskills\u002Ftools-creusot-install\u002FSKILL.md",[],[108,109,78,110,100,111],"tools creusot install","install","rust","tool",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":38},"01M6KP22H28FQ1X0V7VJHEFWXD","tools-creusot-init","Prepare an existing Cargo project to use Creusot formal verification","https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus\u002Fblob\u002Funstable\u002Fcomponents\u002Fzyre\u002F.claude\u002Fskills\u002Ftools-creusot-init\u002FSKILL.md",[],[119,78,120,23,30,121,122,100,123,95,124,125,126],"tools creusot init","init","components","prepare","use","cargo","manager","Existing",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":38},"01M6KP1V506J9YM8DKKVDG1NRE","tools-creusot-coq-install","Add Coq 8.20 as an additional prover to an existing Creusot installation, for verification conditions that SMT solvers cannot discharge","https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus\u002Fblob\u002Funstable\u002Fcomponents\u002Fzyre\u002F.claude\u002Fskills\u002Ftools-creusot-coq-install\u002FSKILL.md",[],[134,135,109,78,97,126,136,137,100,138],"tools creusot coq install","Coq","as","installation","add",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":38},"01M6KP1PQJF3H765TYZAZ7P3EF","tools-creusot-annotate-interfaces","Formally verify a component's properties with Creusot and annotate its interface definitions","https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus\u002Fblob\u002Funstable\u002Fcomponents\u002Fzyre\u002F.claude\u002Fskills\u002Ftools-creusot-annotate-interfaces\u002FSKILL.md",[],[78,146,147,26,82,148,79,149,150],"tools creusot annotate interfaces","annotate","properties","component","interface"]