@plaited/development-skills 0.5.0 → 0.6.1

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
@@ -13,20 +13,13 @@ Before completing a code review, run these validation scripts:
 
 ### AgentSkills Validation
 
-When working with AgentSkills directories (`.claude/skills/`, `.cursor/skills/`, `.factory/skills/`, etc.):
+When working with AgentSkills directories (`.plaited/skills/`, `.claude/skills/`, `.cursor/skills/`, `.factory/skills/`, etc.):
 
 {{#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/documentation.md

@@ -0,0 +1,41 @@
+# Documentation Standards
+
+## TSDoc Requirements
+
+Public APIs require comprehensive TSDoc documentation following these conventions:
+
+- **No `@example` sections** - Tests serve as living examples
+- **Use `@internal` marker** - Mark non-public APIs explicitly
+- **Always use `type`** - Prefer type aliases over interfaces
+
+### TSDoc Template
+
+```typescript
+/**
+ * Brief description of what this does
+ *
+ * @remarks
+ * Additional context, usage notes, or implementation details.
+ *
+ * @param options - Description of the parameter
+ * @returns Description of return value
+ *
+ * @public
+ */
+```
+
+## Diagrams
+
+Use Mermaid diagrams only (not ASCII art):
+
+```markdown
+\```mermaid
+flowchart TD
+    A[Start] --> B[Process]
+    B --> C[End]
+\```
+```
+
+**Avoid**: ASCII box-drawing characters (`┌`, `│`, `└`, `─`, etc.)
+
+**Rationale:** Token efficiency, clearer semantic meaning, easier maintenance.

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

@@ -0,0 +1,31 @@
+# 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/github.md

@@ -58,7 +58,7 @@ gh api repos/<owner>/<repo>/pulls/<number>/comments --jq '
 **Step 4: Address ALL feedback**
 Create a checklist and address each item:
 - [ ] Human reviewer comments
-- [ ] Claude Code review comments
+- [ ] Agentic Code review comments
 - [ ] GitHub Advanced Security alerts (ReDoS, injection, etc.)
 - [ ] GitHub Code Quality comments (dead code, useless assignments)
 - [ ] Inline review suggestions
@@ -68,7 +68,7 @@ Create a checklist and address each item:
 | Source | API/Location | Description |
 |--------|--------------|-------------|
 | Human reviewers | `gh pr view --json reviews` | Code owners, team members |
-| Claude Code | `gh pr view --json comments` | AI-generated review (login: `claude`) |
+| AI code review | `gh pr view --json comments` | AI-generated review |
 | GitHub Advanced Security | `gh api .../code-scanning/alerts` | Security vulnerabilities (ReDoS, injection) |
 | GitHub Code Quality | `gh api .../pulls/.../comments` | Code quality issues (login: `github-code-quality[bot]`) |
 | Inline suggestions | `gh api .../pulls/.../comments` | Line-specific review comments |
@@ -76,9 +76,9 @@ Create a checklist and address each item:
 ### Filtering by Author
 
 ```bash
-# Get all automated reviews from PR
+# Get all automated reviews from PR (adjust regex for your AI reviewer logins)
 gh pr view <number> --repo <owner>/<repo> --json reviews --jq '
-  .reviews[] | select(.author.login | test("github-|claude")) | {author: .author.login, state: .state}
+  .reviews[] | select(.author.login | test("github-|bot")) | {author: .author.login, state: .state}
 '
 
 # Get specific inline comment by ID

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

@@ -1,8 +1,3 @@
-<!--
-RULE TEMPLATE - Distributed via /scaffold-rules
-Variables: {{#if bun}}
--->
-
 # Module Organization
 
 ## No Index Files
@@ -43,9 +38,7 @@ Only use `main.ts` if the package truly has multiple co-equal entry points that
 
 ## Explicit Import Extensions
 
-{{#if bun}}
 Always include `.ts` extensions in imports. Bun runs TypeScript natively—no compilation required:
-{{/if}}
 
 ```typescript
 // ✅ Good

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

@@ -1,8 +1,3 @@
-<!--
-RULE TEMPLATE - Distributed via /scaffold-rules
-Variables: {{#if agent:claude}}
--->
-
 # Testing
 
 Use Bun's built-in test runner for unit and integration tests.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@plaited/development-skills",
-  "version": "0.5.0",
+  "version": "0.6.1",
   "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)
   }