_shared

Define naming conventions and recovery protocols for SDD artifacts.

Updated Mar 26, 2025
One-click install
npx skills add https://github.com/ricardoalt1515/.config --skill shared-ricardoalt1515
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: _shared
Source: https://github.com/ricardoalt1515/.config/tree/main/opencode/skills/_shared
Command: npx skills add https://github.com/ricardoalt1515/.config --skill shared-ricardoalt1515

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires engram, openspec, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides shared reference documents and conventions for installed skills, ensuring consistency and facilitating seamless integration between various skills.

Core Features & Use Cases

  • Shared References: Provides a central repository of shared reference documents consumed by real SDD skills.
  • Conventions: Defines naming rules and recovery protocols for SDD artifacts, ensuring consistency and recoverability.
  • Use Case: When using different SDD skills in a project, this Skill ensures that all artifacts are named and structured according to the same conventions, making them easier to manage and integrate.

Quick Start

Access the shared references within the _shared skill directory to understand the naming conventions and recovery protocols for SDD artifacts.

Frequently Asked Questions about _shared

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I maintain consistency for SDD artifacts across multiple project skills?

To maintain consistency for SDD artifacts, you need shared reference documents and naming conventions to ensure all installed skills structure and name their outputs uniformly. This centralizes artifact management and facilitates seamless integration between various project components.

What are SDD recovery protocols and when do I need them?

SDD recovery protocols are standardized procedures for restoring and accessing structured development artifacts. You need them when managing multiple installed skills to ensure artifacts remain recoverable and consistently structured across different project sessions and environments.

Do I need Engram and OpenSpec to resolve project context for SDD artifacts?

Yes, you need Engram and OpenSpec to resolve project context for SDD artifacts. These dependencies are required for artifact storage and retrieval, enabling the shared conventions and recovery protocols to function correctly across installed skills.

How do I standardize SDD artifact naming conventions in a development project?

To standardize SDD artifact naming conventions, implement a shared repository of reference documents that defines strict naming rules. This ensures all development skills generate artifacts following the same structural guidelines, making them easier to manage and integrate.

Can I use shared SDD references to improve skill recoverability?

Yes, you can use shared SDD references to improve skill recoverability. By providing a central repository of conventions and recovery protocols, the references ensure artifacts are consistently named and structured, making installed skills easier to recover and manage.