metacoding 1.0.0

package/templates/react/files/release.instructions.md

@@ -0,0 +1,72 @@
+---
+description: "Step-by-step release process automation"
+applyTo: "package.json"
+---
+
+# Release Process Checklist
+
+## Pre-Release Validation
+1. **Test Suite:** Verify all tests pass: `npm test`
+2. **Build Verification:** Ensure clean build without errors: `npm run build`
+3. **Linting:** Check code quality standards: `npm run lint`
+4. **Dependencies:** Review and update dependencies if needed
+5. **Security Audit:** Run security audit: `npm audit`
+
+## Version Management
+1. **Semantic Versioning:** Update version in package.json following SemVer:
+   - **MAJOR:** Breaking changes (X.0.0)
+   - **MINOR:** New features, backward compatible (0.X.0)
+   - **PATCH:** Bug fixes, backward compatible (0.0.X)
+2. **Version Consistency:** Ensure version matches across all relevant files
+3. **Breaking Changes:** Document breaking changes prominently in changelog
+
+## Documentation Updates
+1. **README.md Updates:**
+   - Update version badges to match package.json version
+   - Refresh installation instructions if needed
+   - Update feature descriptions for new capabilities
+   - Verify all links and examples work correctly
+2. **API Documentation:** Update API docs for any interface changes
+
+## Changelog Management
+1. **Add New Entry:** Create new section in CHANGELOG.md with:
+   - Release version number (matching package.json)
+   - Release date in YYYY-MM-DD format
+   - Grouped changes by category:
+     - **Added:** New features
+     - **Changed:** Changes in existing functionality
+     - **Deprecated:** Soon-to-be removed features
+     - **Removed:** Now removed features
+     - **Fixed:** Bug fixes
+     - **Security:** Security vulnerability fixes
+2. **Entry Guidelines:**
+   - Keep entries brief but descriptive (1-2 lines per change)
+   - Focus on user impact rather than technical implementation
+   - Reference issue/PR numbers when applicable: `(#123)`
+   - Highlight breaking changes with ⚠️ or **BREAKING:**
+
+## Git Operations
+1. **Commit Changes:** Stage all release-related changes
+2. **Commit Message:** Use format: `chore: bump version to vX.Y.Z`
+3. **Create Tag:** Tag the commit with version number: `git tag vX.Y.Z`
+4. **Push Changes:** Push commits and tags: `git push && git push --tags`
+
+## GitHub Release
+1. **Create Release:** Create GitHub release with tag matching package.json version
+2. **Release Title:** Use format: `vX.Y.Z - [Brief description]`
+3. **Release Notes:** 
+   - Copy relevant sections from CHANGELOG.md
+   - Include installation instructions
+   - Highlight major changes and breaking changes
+   - Thank contributors if applicable
+
+## Post-Release Verification
+1. **Package Registry:** Verify package published correctly (if applicable)
+2. **Installation Test:** Test installation from registry in clean environment
+3. **Documentation Links:** Ensure all documentation links work correctly
+4. **Monitor Issues:** Watch for any immediate issues reported by users
+
+## Rollback Plan
+- **Git Revert:** Know how to revert problematic releases
+- **Package Unpublish:** Understand package registry policies for unpublishing
+- **Communication:** Prepare communication strategy for critical issues

package/templates/react/files/test-runner.instructions.md

@@ -0,0 +1,108 @@
+---
+description: 'Instructions for running and maintaining tests'
+applyTo: 'test/**/*.ts'
+---
+
+# Test Execution Guidelines
+
+## Pre-Commit Testing
+
+- Run all tests before committing changes: `npm test`
+- Ensure tests pass in both development and CI environments
+- Fix failing tests before proceeding with commits
+- Run specific test suites for targeted changes when appropriate
+
+## Test Development Standards
+
+- **New Features:** Ensure all new features have corresponding unit tests
+- **Test Coverage:** Aim for high coverage of critical functionality paths
+- **Test Documentation:** Follow table format in `test/test-documentation.md` for all test cases
+- **Test Organization:** Group related tests in describe blocks with clear hierarchy
+
+## Test Case Documentation Format
+
+All test cases must be documented using the standardized table format:
+
+```markdown
+| Test Case ID  | Description                                 | Type | Status    |
+| :------------ | :------------------------------------------ | :--- | :-------- |
+| AREA-TYPE-001 | Brief but descriptive test case description | Unit | Completed |
+```
+
+## Test Case Naming Conventions
+
+### Test Case ID Format: `[AREA]-[TYPE]-[NUMBER]`
+
+**Area Prefixes (React/Frontend specific):**
+
+- `COMP` - React component tests
+- `HOOK` - Custom hooks tests
+- `PAGE` - Page/Route component tests
+- `STORE` - State management tests (Redux/Zustand)
+- `API` - API service layer tests
+- `UTIL` - Utility function tests
+- `AUTH` - Authentication flow tests
+- `FORM` - Form validation tests
+- `DOC` - Documentation Quality tests
+- `E2E` - End-to-End workflow tests
+- `INT` - Integration tests
+
+**Type Suffixes:**
+
+- `UNIT` - Unit tests
+- `INT` - Integration tests
+- `E2E` - End-to-end tests
+
+**Examples:**
+
+- `COMP-UNIT-001` - First unit test for React Components
+- `HOOK-UNIT-001` - First unit test for Custom Hooks
+- `API-INT-001` - First integration test for API Services
+- `E2E-WF-001` - First end-to-end workflow test
+
+### Test Method Naming
+
+- Format: `methodName_scenario_expectedOutcome`
+- Example: `getUserById_userExists_returnsUserObject`
+- Use camelCase for all test method names
+
+## Test Data Management
+
+- **Fixtures:** Update test fixtures when data structures change
+- **Realistic Data:** Use realistic data in integration tests to catch real-world issues
+- **Mock Strategy:** Mock external dependencies in unit tests for isolation
+- **Test Database:** Use separate test database/environment for integration tests
+- **Temporary File Cleanup:** Clean up all temporary test files, debug outputs, and mock data after test execution
+- **Fixture Organization:** Move reusable test data to `/test/fixtures/` directory for proper organization
+
+## Test File Hygiene
+
+- **No Orphaned Files:** Remove temporary test files created during debugging or development
+- **Debug Output Cleanup:** Remove console.log statements and debug files before committing
+- **Test Artifact Management:** Ensure test screenshots, logs, and reports are properly managed or cleaned up
+- **Resource Management:** Properly dispose of file handles, database connections, and other test resources
+
+## Test Types and Patterns
+
+- **Unit Tests:** Test individual functions, methods, and components in isolation
+- **Integration Tests:** Test feature workflows and component interactions
+- **End-to-End Tests:** Test complete user scenarios and workflows
+- **Regression Tests:** Add tests for previously fixed bugs to prevent recurrence
+
+## Performance Testing
+
+- **Test Execution Speed:** Keep unit tests fast (under 100ms each when possible)
+- **Parallel Execution:** Structure tests to run safely in parallel
+- **Resource Cleanup:** Ensure proper cleanup of test resources and temporary data
+- **Memory Management:** Monitor and prevent memory leaks in long-running test suites
+
+## Test Maintenance
+
+- **Regular Review:** Periodically review and refactor outdated tests
+- **Documentation:** Document complex test scenarios and their purposes
+- **Continuous Updates:** Update tests when requirements or APIs change
+- **Test Quality:** Apply the same code quality standards to test code as production code
+- **Update test-documentation.md:** Add new test cases to the appropriate table section
+- **Status Tracking:** Update test status as development progresses
+- **Table Format:** Maintain consistent table formatting and column alignment
+- **ID Assignment:** Assign sequential IDs within each area (AREA-TYPE-001, AREA-TYPE-002, etc.)

package/templates/react/template.json

@@ -0,0 +1,14 @@
+{
+  "name": "react",
+  "description": "React frontend development template with modern patterns and best practices",
+  "prompts": [],
+  "vscodeSettings": {
+    "github.copilot.chat.codeGeneration.useInstructionFiles": true,
+    "chat.promptFiles": true,
+    "editor.formatOnSave": true,
+    "editor.codeActionsOnSave": {
+      "source.organizeImports": true,
+      "source.fixAll.eslint": true
+    }
+  }
+}