@sylphx/flow 2.29.3 → 3.0.0

package/assets/slash-commands/quality.md

@@ -1,181 +0,0 @@
----
-name: quality
-description: Improve test coverage, fix tests, optimize performance, reduce bundle size
----
-
-# Quality Assurance
-
-Maximize quality metrics: tests, coverage, performance, bundle size.
-
-## Scope
-
-**Testing:**
-- Fix failing tests
-- Add missing tests (.test.ts for all modules)
-- Improve coverage (critical paths 100%, business logic 80%+)
-- Test edge cases
-- Test error paths
-- Integration tests
-- E2E tests (if applicable)
-
-**Benchmarking:**
-- Add benchmarks (.bench.ts for critical functions)
-- Measure performance
-- Identify regressions
-- Optimize slow operations
-
-**Performance:**
-- Profile hot paths
-- Optimize algorithms (reduce complexity)
-- Fix memory leaks
-- Reduce allocations
-- Cache expensive operations
-- Lazy load where possible
-
-**Bundle Size:**
-- Analyze bundle composition
-- Remove unused dependencies
-- Tree-shake effectively
-- Code split strategically
-- Compress assets
-- Use dynamic imports
-
-**Code Quality:**
-- Fix lint errors/warnings
-- Improve type safety (no `any`)
-- Reduce complexity
-- Improve maintainability
-- Follow code standards
-
-**Security:**
-- Fix vulnerabilities
-- Update dependencies
-- Validate inputs
-- Sanitize outputs
-- Secure defaults
-
-## Execution
-
-### 1. Test Coverage
-
-```bash
-# Run tests with coverage
-npm run test:coverage
-
-# Identify gaps
-# Add tests for uncovered code
-# Focus on critical paths first
-```
-
-**Priority:**
-- Critical business logic (100%)
-- Error handling (100%)
-- Edge cases (90%)
-- Happy paths (100%)
-- Integration points (80%)
-
-### 2. Benchmarking
-
-```bash
-# Run benchmarks
-npm run bench
-
-# Compare against baseline
-# Identify regressions
-# Optimize bottlenecks
-```
-
-**Add benchmarks for:**
-- Algorithm complexity (O(n) vs O(n²))
-- Database queries
-- API calls
-- Data processing
-- Rendering (if UI)
-
-### 3. Performance Profiling
-
-```bash
-# Profile application
-node --inspect ...
-# Or use Clinic.js, 0x, etc.
-
-# Identify bottlenecks
-# Optimize hot paths
-# Measure improvements
-```
-
-**Check:**
-- CPU usage
-- Memory usage
-- I/O operations
-- Network calls
-- Rendering time
-
-### 4. Bundle Analysis
-
-```bash
-# Analyze bundle
-npm run build -- --analyze
-
-# Check size
-ls -lh dist/
-
-# Identify large dependencies
-# Remove unnecessary code
-```
-
-**Optimize:**
-- Remove unused dependencies
-- Use smaller alternatives
-- Dynamic imports for large modules
-- Tree-shake effectively
-- Minify properly
-
-### 5. Quality Metrics
-
-**Track:**
-- Test coverage: `npm run test:coverage`
-- Bundle size: `ls -lh dist/`
-- Performance: `npm run bench`
-- Security: `npm audit`
-- Type coverage: TypeScript strict mode
-- Lint score: `npm run lint`
-
-## Targets
-
-**Tests:**
-- Coverage: ≥80% (business logic ≥90%)
-- All critical paths: 100%
-- Build time: <30s
-- Test time: <10s
-
-**Performance:**
-- Page load: <3s
-- API response: <200ms
-- Time to interactive: <5s
-- Bundle size: <100KB (gzipped)
-
-**Quality:**
-- Zero lint errors
-- Zero `any` types (unless justified)
-- Zero security vulnerabilities (high/critical)
-- Complexity score: <10 per function
-
-## Commit Strategy
-
-Atomic commits per improvement:
-- `test(auth): add tests for token validation`
-- `perf(db): optimize user query with batch loading`
-- `build: reduce bundle size by 40% with code splitting`
-
-## Exit Criteria
-
-- [ ] All tests pass
-- [ ] Coverage meets targets
-- [ ] Benchmarks added for critical functions
-- [ ] Performance optimized
-- [ ] Bundle size reduced
-- [ ] No security vulnerabilities
-- [ ] Quality metrics improved
-
-Report: Coverage %, bundle size reduction, performance gains, benchmarks added.

package/assets/slash-commands/release.md

@@ -1,103 +0,0 @@
----
-name: release
-description: Publish new version and monitor release process
----
-
-# Release & Publish
-
-Prepare, publish, and monitor package release.
-
-## Pre-Release Checks
-
-**Quality Gates:**
-- [ ] All tests pass
-- [ ] No lint errors
-- [ ] Build successful
-- [ ] No security vulnerabilities
-- [ ] Dependencies up to date
-- [ ] CHANGELOG updated
-- [ ] README accurate
-- [ ] Breaking changes documented
-
-**Version Decision:**
-- Breaking changes → `major`
-- New features → `minor` (default)
-- Bug fixes → `patch`
-
-## Release Process
-
-### For TypeScript/JavaScript Projects
-
-1. **Create Changeset:**
-   ```bash
-   bunx changeset
-   ```
-   - Select package
-   - Choose version bump type
-   - Write clear summary
-
-2. **Version Bump:**
-   ```bash
-   bunx changeset version
-   ```
-   - Updates package.json
-   - Updates CHANGELOG.md
-   - Consumes changeset
-
-3. **Commit & Push:**
-   ```bash
-   git add -A
-   git commit -m "chore(release): <package>@<version>"
-   git push
-   ```
-
-4. **Monitor CI:**
-   ```bash
-   gh run list --workflow=release --limit 5
-   gh run watch <run-id>
-   ```
-
-5. **Verify Publication:**
-   ```bash
-   npm view <package>@<version>
-   ```
-
-### For Other Projects
-
-1. Update version in manifest (package.json, setup.py, etc.)
-2. Update CHANGELOG
-3. Create git tag
-4. Push tag to trigger release
-5. Monitor CI/CD
-
-## Post-Release
-
-- [ ] Verify package published
-- [ ] Test installation: `npm install <package>@latest`
-- [ ] Create GitHub release with notes
-- [ ] Announce (if public package)
-- [ ] Close related issues/PRs
-
-## Troubleshooting
-
-**CI fails on install:**
-- Update lockfile locally: `bun install`
-- Commit and push
-
-**Tests fail in CI:**
-- Run tests locally: `npm test`
-- Fix issues, commit, push
-
-**Build fails:**
-- Check build locally: `npm run build`
-- Fix errors, commit, push
-
-## Exit Criteria
-
-- [ ] Package published successfully
-- [ ] CI workflow completed
-- [ ] GitHub release created
-- [ ] Version verified on registry
-- [ ] Installation tested
-
-Report: Version number, publish time, registry URL.

package/assets/slash-commands/review.md

@@ -1,44 +0,0 @@
----
-name: review
-description: Review codebase by topic - /review <what to review>
-args:
-  - name: topic
-    description: What to review (e.g., auth, security, "the login flow", "why it's slow")
-    required: true
----
-
-# Review: $ARGS
-
-## Mandate
-
-- **Think like the failure mode.** Security → attacker. Performance → slow network. Auth → confused user.
-- **Delegate workers** for parallel research. You synthesize and verify.
-- **Fix, don't report.** Implement solutions directly.
-
-## Execution
-
-1. **Load skills** — Use the Skill tool to load guidelines for relevant domains. Read the guidelines.
-
-2. **Understand** — How is this implemented? Architecture, choices, tradeoffs.
-
-3. **Find issues** — What violates the guidelines? What's wrong and why it matters?
-
-4. **Fix** — Implement solutions directly.
-
-## Output
-
-```
-## Review: [topic]
-
-### Understanding
-[Architecture, choices, tradeoffs]
-
-### Issues
-[What's wrong and why]
-
-### Fixed
-[Changes made]
-
-### Remains
-[Needs human decision]
-```