@plaited/development-skills 0.5.0 → 0.6.0

package/{.claude → .plaited}/rules/accuracy.md

@@ -1,6 +1,6 @@
 <!--
-RULE TEMPLATE - Distributed via /scaffold-rules
-Variables: {{LINK:testing}}, {{#if development-skills}}, {{#if supports-slash-commands}}
+RULE TEMPLATE - Distributed via scaffold-rules skill
+Variables: {{LINK:testing}}, {{#if development-skills}}
 -->
 
 # Accuracy and Confidence Standards
@@ -19,7 +19,7 @@ Variables: {{LINK:testing}}, {{#if development-skills}}, {{#if supports-slash-co
 {{#if development-skills}}
    - **For TypeScript/JavaScript projects**: When @plaited/development-skills is installed, prefer LSP tools for type-aware verification:
      - Use `lsp-find` to search for symbols, types, and patterns across the workspace
-     - Use `lsp-references` to find all usages of a symbol
+     - Use `lsp-refs` to find all usages of a symbol
      - Use `lsp-hover` to verify type signatures
      - Use `lsp-analyze` for batch analysis of file structure
 {{/if}}
@@ -30,14 +30,7 @@ Variables: {{LINK:testing}}, {{#if development-skills}}, {{#if supports-slash-co
 4. **Tool-Assisted Verification**: Use available tools to enhance verification accuracy:
 {{#if development-skills}}
    - **TypeScript LSP tools** (when available): Use for type-aware analysis of `.ts`, `.tsx`, `.js`, `.jsx` files
-{{/if}}
-{{#if supports-slash-commands}}
-     - Available via `/lsp-hover`, `/lsp-find`, `/lsp-refs`, `/lsp-analyze` commands
-{{/if}}
-{{^if supports-slash-commands}}
-{{#if development-skills}}
      - Available via `bunx @plaited/development-skills lsp-*` commands
-{{/if}}
 {{/if}}
    - **WebFetch**: Retrieve current documentation from authoritative sources (MDN Web Docs, WHATWG specs) when using web platform APIs
    - These tools complement (but do not replace) reading live code - always verify outputs against actual implementation

package/{.claude → .plaited}/rules/code-review.md

@@ -1,6 +1,6 @@
 <!--
-RULE TEMPLATE - Distributed via /scaffold-rules
-Variables: {{#if development-skills}}, {{#if supports-slash-commands}}
+RULE TEMPLATE - Distributed via scaffold-rules skill
+Variables: {{#if development-skills}}
 -->
 
 # Code Review Standards
@@ -17,16 +17,9 @@ When working with AgentSkills directories (`.claude/skills/`, `.cursor/skills/`,
 
 {{#if development-skills}}
 **Validate structure:**
-{{#if supports-slash-commands}}
-```
-/validate-skill <path>
-```
-{{/if}}
-{{^if supports-slash-commands}}
 ```bash
 bunx @plaited/development-skills validate-skill <path>
 ```
-{{/if}}
 
 This checks:
 - SKILL.md exists with required frontmatter (name, description)

package/.plaited/rules/git-workflow.md

@@ -0,0 +1,36 @@
+<!--
+RULE TEMPLATE - Distributed via scaffold-rules skill
+Variables: {{LINK:*}}
+-->
+
+# Git Workflow
+
+## Commit Message Format
+
+Use multi-line commit messages for detailed changes:
+
+```bash
+git commit -m "refactor: description here
+
+Additional context on second line."
+```
+
+## Pre-commit Hooks
+
+**Never use `--no-verify`** to bypass pre-commit hooks. If hooks fail, it indicates a real issue that must be fixed:
+
+1. Investigate the error message
+2. Fix the underlying issue (lint errors, format issues, test failures)
+3. Re-run the commit
+
+Using `--no-verify` masks problems and defeats the purpose of automated quality checks.
+
+## Commit Conventions
+
+Follow conventional commits format:
+- `feat:` - New features
+- `fix:` - Bug fixes
+- `refactor:` - Code changes that neither fix bugs nor add features
+- `docs:` - Documentation only changes
+- `chore:` - Maintenance tasks
+- `test:` - Adding or updating tests

package/{.claude → .plaited}/rules/module-organization.md

@@ -1,5 +1,5 @@
 <!--
-RULE TEMPLATE - Distributed via /scaffold-rules
+RULE TEMPLATE - Distributed via scaffold-rules skill
 Variables: {{#if bun}}
 -->
 

package/{.claude → .plaited}/rules/testing.md

@@ -1,5 +1,5 @@
 <!--
-RULE TEMPLATE - Distributed via /scaffold-rules
+RULE TEMPLATE - Distributed via scaffold-rules skill
 Variables: {{#if agent:claude}}
 -->
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@plaited/development-skills",
-  "version": "0.5.0",
+  "version": "0.6.0",
   "description": "Development skills for Claude Code - TypeScript LSP, code documentation, and validation tools",
   "license": "ISC",
   "engines": {
@@ -21,7 +21,7 @@
   "files": [
     "bin/",
     "src/",
-    ".claude/"
+    ".plaited/"
   ],
   "publishConfig": {
     "access": "public"

package/src/lsp-analyze.ts

@@ -211,7 +211,7 @@ Examples:
 
     console.log(JSON.stringify(result, null, 2))
   } catch (error) {
-    console.error(`Error: ${error}`)
+    console.error('Error:', error)
     await client.stop()
     process.exit(1)
   }

package/src/lsp-find.ts

@@ -69,7 +69,7 @@ export const lspFind = async (args: string[]) => {
 
     console.log(JSON.stringify(result, null, 2))
   } catch (error) {
-    console.error(`Error: ${error}`)
+    console.error('Error:', error)
     await client.stop()
     process.exit(1)
   }

package/src/lsp-hover.ts

@@ -75,7 +75,7 @@ export const lspHover = async (args: string[]) => {
       console.log('null')
     }
   } catch (error) {
-    console.error(`Error: ${error}`)
+    console.error('Error:', error)
     await client.stop()
     process.exit(1)
   }

package/src/lsp-references.ts

@@ -71,7 +71,7 @@ export const lspRefs = async (args: string[]) => {
 
     console.log(JSON.stringify(result, null, 2))
   } catch (error) {
-    console.error(`Error: ${error}`)
+    console.error('Error:', error)
     await client.stop()
     process.exit(1)
   }

package/src/lsp-symbols.ts

@@ -61,7 +61,7 @@ export const lspSymbols = async (args: string[]) => {
 
     console.log(JSON.stringify(result, null, 2))
   } catch (error) {
-    console.error(`Error: ${error}`)
+    console.error('Error:', error)
     await client.stop()
     process.exit(1)
   }