# Update Core DSL Processing Safely

Core DSL changes can break validation, normalization, diffing, and patch behavior. This skill gives Claude, Codex, and Claude Code a focused workflow for safe core package updates.

## Install

```bash
npx skillstore add 7nohe/core-development
```

## Metadata

- Status: approved
- Slug: 7nohe-core-development
- Skillstore revision: r1
- Version status: missing
- Tree hash: 20d18ba31f0dd530bc70badfed39211af5b3c233bf1294d4d37f9bada154c2d0
- Author: 7nohe
- GitHub username: 7nohe
- License: MIT
- Repository: https://github.com/7nohe/figram/tree/main/.claude/skills/core-development
- Ref: e9e4712298ed071d92417a41714be123eb8364fa
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 79
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/7nohe-core-development
- Manifest: https://skillstore.pages.dev/api/skills/7nohe-core-development/manifest

## Capabilities

- Identifies the core package as packages/core and explains its dependency-free role.
- Maps DSL validation, normalization, IR conversion, diffing, and patch generation flow.
- Lists key TypeScript files for types, validation, normalization, and diff logic.
- Describes node and edge type relationships between DSL input and normalized IR.
- Provides workflow steps for adding node or edge properties with matching tests.
- Documents Bun test commands for all core tests and focused test files.

## Use Cases

- Add a DSL Node Property: Update type definitions, validation, normalization defaults, diff behavior, and tests for a new node field.
- Tighten YAML Validation: Revise validation rules while preserving the expected DSL to IR processing flow.
- Debug Patch Output: Trace how normalized documents become patch operations and identify missing diff cases.

## Prompt Templates

### Review a Core Change

```
Review this proposed core package change: [describe change]. Tell me which files in packages/core need updates and which tests should be added.
```

### Add a Node Field

```
Help me add a new DSL node property named [field]. Update the plan for types, validation, normalization defaults, diff behavior, and tests.
```

### Change Validation Rules

```
I need to change validation for [rule]. Check how validate, normalize, and diff should respond, then identify focused test cases.
```

### Audit Diff Semantics

```
Analyze the diff behavior for [scenario]. Verify expected patch operations, edge cases, and revision handling in the core package.
```

## Limitations

- It only describes the core package workflow and does not implement changes by itself.
- It assumes the repository uses the file names and package paths shown in SKILL.md.
- It does not cover UI, CLI, deployment, or package release workflows.
- It does not replace a full security review of WebSocket secret handling.

## Best Practices

- Update types, validation, normalization, diff logic, and tests together for schema changes.
- Keep core package changes dependency-free unless the project requirements explicitly change.
- Run focused Bun tests after changing validation, normalization, or diff behavior.

## Anti Patterns

- Do not add DSL fields in types without validation and normalization coverage.
- Do not change diff equality rules without tests for added, removed, and updated items.
- Do not treat WebSocket protocol examples as production security guidance.

## Security Audit

- Audited at: 2026-07-04T17:24:49.788\+00:00
- Summary: Most static findings are markdown backticks, diagrams, or TypeScript examples, not Ruby shell execution. The only command text is hardcoded Bun test guidance scoped to packages/core. No prompt injection, data exfiltration, or malicious intent was found in SKILL.md.

## Stats

- Views: 221
- Downloads: 17
- Favorites: 0
- Popularity score: 0