@intentsolutionsio/sugar 2.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,26 @@
1
+ # Skill Assets
2
+
3
+ This directory contains static assets used by this skill.
4
+
5
+ ## Purpose
6
+
7
+ Assets can include:
8
+ - Configuration files (JSON, YAML)
9
+ - Data files
10
+ - Templates
11
+ - Schemas
12
+ - Test fixtures
13
+
14
+ ## Guidelines
15
+
16
+ - Keep assets small and focused
17
+ - Document asset purpose and format
18
+ - Use standard file formats
19
+ - Include schema validation where applicable
20
+
21
+ ## Common Asset Types
22
+
23
+ - **config.json** - Configuration templates
24
+ - **schema.json** - JSON schemas
25
+ - **template.yaml** - YAML templates
26
+ - **test-data.json** - Test fixtures
@@ -0,0 +1,26 @@
1
+ # Skill References
2
+
3
+ This directory contains reference materials that enhance this skill's capabilities.
4
+
5
+ ## Purpose
6
+
7
+ References can include:
8
+ - Code examples
9
+ - Style guides
10
+ - Best practices documentation
11
+ - Template files
12
+ - Configuration examples
13
+
14
+ ## Guidelines
15
+
16
+ - Keep references concise and actionable
17
+ - Use markdown for documentation
18
+ - Include clear examples
19
+ - Link to external resources when appropriate
20
+
21
+ ## Types of References
22
+
23
+ - **examples.md** - Usage examples
24
+ - **style-guide.md** - Coding standards
25
+ - **templates/** - Reusable templates
26
+ - **patterns.md** - Design patterns
@@ -0,0 +1,24 @@
1
+ # Skill Scripts
2
+
3
+ This directory contains optional helper scripts that support this skill's functionality.
4
+
5
+ ## Purpose
6
+
7
+ Scripts here can be:
8
+ - Referenced by the skill for automation
9
+ - Used as examples for users
10
+ - Executed during skill activation
11
+
12
+ ## Guidelines
13
+
14
+ - All scripts should be well-documented
15
+ - Include usage examples in comments
16
+ - Make scripts executable (`chmod +x`)
17
+ - Use `#!/bin/bash` or `#!/usr/bin/env python3` shebangs
18
+
19
+ ## Adding Scripts
20
+
21
+ 1. Create script file (e.g., `analyze.sh`, `process.py`)
22
+ 2. Add documentation header
23
+ 3. Make executable: `chmod +x script-name.sh`
24
+ 4. Test thoroughly before committing