metacoding 1.0.0

package/CHANGELOG.md

@@ -0,0 +1,91 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [1.0.0] - 2025-06-21
+
+### Added
+
+- **NPM Package Distribution**: Complete transformation from manual file copying to professional npm package
+- **Interactive CLI Tool**: `metacoding` command with init, validate, and update subcommands
+- **Template System**: Configurable templates for different project types (general, react, node, python)
+- **Project Detection**: Automatic detection of project type, tech stack, and existing configuration
+- **VS Code Integration**: Automatic VS Code settings configuration for GitHub Copilot
+- **Interactive Setup**: Guided project configuration with prompts for project details
+- **TypeScript Implementation**: Full TypeScript codebase with comprehensive type definitions
+- **Test Suite**: Unit and integration tests with >80% coverage target
+- **Professional CLI Experience**: Color output, progress indicators, and helpful error messages
+
+### Changed
+
+- **Installation Method**: From manual file download to simple `npm install -g metacoding`
+- **Setup Process**: From 6-step manual process to single `metacoding init` command
+- **User Experience**: From error-prone manual setup to guided, validated automation
+- **Template Processing**: Dynamic variable substitution for project-specific customization
+- **File Management**: Automatic directory creation, file validation, and conflict resolution
+
+### Technical Details
+
+- **Dependencies**: Commander.js for CLI, Inquirer for prompts, Chalk for colors, fs-extra for file operations
+- **Build System**: TypeScript compilation with source maps and declarations
+- **Testing**: Jest test framework with coverage reporting
+- **Code Quality**: ESLint, Prettier, and strict TypeScript configuration
+- **Distribution**: Professional npm package with proper semver and release management
+
+### Breaking Changes
+
+- **Installation**: Manual setup method is deprecated in favor of npm package
+- **File Structure**: Templates now use `{{VARIABLE}}` syntax instead of `[placeholder]` format
+
+### Migration Guide
+
+Existing manual installations can be migrated by:
+
+1. Installing the npm package: `npm install -g metacoding`
+2. Running `metacoding validate` to check current setup
+3. Running `metacoding update` to migrate to latest format
+
+## [Unreleased]
+
+### Added
+
+- **Mandatory Development Workflow**: 7-step enforced process for all development tasks
+  - Task understanding and planning with user confirmation
+  - Task management with status tracking
+  - Test-Driven Development (TDD) approach
+  - Implementation and verification steps
+  - Documentation and status updates
+  - Version control requirements
+  - Workflow completion checks
+- **Status Transparency Guidelines**: Documentation standards for clear status indication
+  - Prohibition of "planned" or "to-do" in titles and headers
+  - Standardized status indicators (✅ 🚧 ❌ ⚠️ 🔄)
+  - Checkbox format for task status tracking
+  - Present-tense headers reflecting current state
+- **Workflow Enforcement Rules**: Quality gates and violation handling procedures
+- **Enhanced Role and Persona**: Updated to emphasize strict workflow adherence
+
+### Changed
+
+- **Main Template**: Updated `copilot-instructions.md` with comprehensive workflow section
+- **Documentation Instructions**: Enhanced `docs-update.instructions.md` with status guidelines
+- **README**: Expanded to include workflow details and status transparency standards
+- **File Structure**: Added `/_meta` and `/test` directories for task and test documentation
+
+### Enhanced
+
+- Code quality through mandatory TDD approach
+- Documentation accuracy with status-transparent language
+- Team collaboration with consistent workflow enforcement
+- Risk mitigation through incremental, tested changes
+
+## [1.0.0] - 2025-06-21
+
+### Added
+
+- Initial project structure
+- Core documentation files
+- Basic instruction templates

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 GitHub Copilot Instructions Template
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,244 @@
+# metacoding: Guided Development Workflow for GitHub Copilot
+
+[![Version](https://img.shields.io/npm/v/metacoding.svg)](https://www.npmjs.com/package/metacoding)
+[![License](https://img.shields.io/badge/License-MIT-blue.svg)](https://opensource.org/licenses/MIT)
+[![GitHub Copilot](https://img.shields.io/badge/GitHub%20Copilot-Compatible-brightgreen.svg)](https://github.com/features/copilot)
+
+Transform your development experience with AI-guided coding standards, structured workflows, and quality practices that help you build better software from day one.
+
+## Table of Contents
+
+- [🎯 What is metacoding?](#-what-is-metacoding)
+- [🛠 Installation Guide](#-installation-guide)
+- [📦 Using the metacoding CLI](#-using-the-metacoding-cli)
+- [💬 How to Use metacoding with GitHub Copilot](#-how-to-use-metacoding-with-github-copilot)
+- [🆘 Getting Help](#-getting-help)
+- [🤝 Contributing](#-contributing)
+- [📄 License](#-license)
+
+## 🎯 What is metacoding?
+
+metacoding is a **guided development methodology** that uses GitHub Copilot's custom instruction capabilities to help developers at any level follow established best practices. Instead of just getting code suggestions, you get:
+
+- **Structured workflows** that guide you through proven development practices
+- **Quality standards** that help you avoid common mistakes
+- **Test-driven development** that's encouraged and guided step-by-step
+- **Documentation guidance** that keeps your projects maintainable
+
+## 🛠 Installation Guide
+
+### Prerequisites
+
+Before installing metacoding, make sure you have:
+
+1. **Visual Studio Code** installed ([download here](https://code.visualstudio.com/))
+2. **GitHub Copilot extension** installed and configured in VS Code
+3. **Active GitHub Copilot subscription** ([get one here](https://github.com/features/copilot))
+4. **Node.js** (version 16 or higher) for the CLI tool
+
+### Quick Setup (Recommended)
+
+The easiest way to get started with metacoding is using our npm package:
+
+1. **Install globally:** `npm install -g metacoding`
+2. **Navigate to your project:** `cd your-project`
+3. **Initialize metacoding:** `metacoding init`
+4. **Follow the interactive prompts and you're done!**
+
+**Available templates:** You can also specify a template during initialization:
+
+- `metacoding init --template react` - Use React template
+- `metacoding init --template node` - Use Node.js/Backend template
+- `metacoding init --template python` - Use Python template
+- `metacoding init --force` - Overwrite existing files
+
+**Note:** The CLI will automatically configure VS Code settings for custom instructions. If you need to configure manually, add these settings to your VS Code settings.json:
+
+```json
+{
+  "github.copilot.chat.codeGeneration.useInstructionFiles": true,
+  "chat.promptFiles": true
+}
+```
+
+After you finished, your project should now look like this:
+
+```
+my-awesome-project/
+├── .github/
+│   ├── copilot-instructions.md
+│   └── instructions/
+│       ├── test-runner.instructions.md
+│       ├── release.instructions.md
+│       ├── docs-update.instructions.md
+│       └── code-review.instructions.md
+```
+
+### Test Your Setup
+
+1. **Restart VS Code** to ensure all settings are applied
+2. **Create a new file** in your project (e.g., `test.js` or `main.py`)
+3. **Open GitHub Copilot Chat:**
+   - Press `Ctrl+Shift+P` (Windows/Linux) or `Cmd+Shift+P` (Mac)
+   - Type "GitHub Copilot: Open Chat"
+   - Press Enter
+4. **Test the setup:**
+   - In GitHub Copilot, ask: "What is the development workflow for this project?"
+   - Copilot should reference your custom instructions and provide project-specific guidance!
+
+## ✅ You're Ready to Go!
+
+## 📦 Using the metacoding CLI
+
+Once installed, you can use these commands:
+
+### `metacoding validate`
+
+Check your current metacoding setup:
+
+- `metacoding validate` - Basic validation
+- `metacoding validate --strict` - Strict validation rules
+- `metacoding validate --fix` - Auto-fix issues where possible
+
+### `metacoding update`
+
+Update your metacoding setup to the latest version:
+
+- `metacoding update` - Update to latest version
+- `metacoding update --backup` - Create backup before updating
+
+### Help and Version
+
+- `metacoding --help` - Show all commands
+- `metacoding --version` - Show version number
+
+## 💬 How to Use metacoding with GitHub Copilot
+
+Once you have metacoding set up, you can leverage its power in several ways:
+
+### Automatic Context Application
+
+GitHub Copilot automatically applies relevant instruction files based on the files you're editing:
+
+- **Editing test files** → `test-runner.instructions.md` automatically applies
+- **Editing Markdown files** → `docs-update.instructions.md` automatically applies
+- **Editing any code file** → `code-review.instructions.md` is available for manual use
+- **Editing package.json** → `release.instructions.md` automatically applies
+
+### Attaching Instruction Files
+
+1. **Open GitHub Copilot Chat** (`Ctrl+Shift+P` → "GitHub Copilot: Open Chat")
+2. **Click the paperclip icon** (attach button) in the Copilot input
+3. **Select "Instructions..."** from the menu
+4. **Choose the instruction file** you want to reference
+5. **Type your prompt** and Copilot will use that instruction context
+
+Examples of effective prompts:
+
+- "Run tests and prepare for publishing changes"
+- "Bump version and commit following release workflow"
+- "Review this code for security vulnerabilities"
+
+### Manual Instruction Reference
+
+You can explicitly reference specific instruction files in GitHub Copilot:
+
+- "Use release.instructions.md to help me bump the version to 2.1.0"
+
+- "Apply code-review.instructions.md guidelines to review this function"
+
+- "Following test-runner.instructions.md, help me write tests for this component"
+
+## Best Practices for Using GitHub Copilot
+
+### Choose the Right Mode for Your Task
+
+- **Agent Mode (Default)**: Use for complex workflows, multi-step tasks, and when you want Copilot to handle the entire process
+  - Examples: "Implement user authentication with tests and documentation" or "Prepare release with version bump and changelog"
+- **Ask Mode**: Use for questions, explanations, and when you need information without taking action
+  - Examples: "Explain how this algorithm works" or "What are the best practices for error handling?"
+- **Edit Mode**: Use for focused code modifications when you want direct file editing
+  - Examples: "Refactor this function to use async/await" or "Add error handling to this method"
+
+### Effective Prompting Strategies
+
+- **Start with simple prompts** like "Let's plan feature X" to test your setup
+- **Be specific about context** when manually referencing instructions
+- **Reference multiple instructions** when needed for complex tasks
+- **Provide necessary context**: include documentation, task list, test cases and related files and folders in your prompt (use the "Attach" menu)
+
+## 🆘 Getting Help
+
+### Common Questions
+
+**Q: Do I need to be an experienced developer?**
+A: No! metacoding provides guidance and structure to help developers at any level adopt proven practices and improve their skills.
+
+**Q: What if I don't have GitHub Copilot?**
+A: You'll need an active GitHub Copilot subscription to use metacoding. Students can get it free through GitHub Education.
+
+**Q: Can I use this without the CLI tool?**
+A: The CLI tool provides the easiest setup experience. For manual setup, you can download instruction files from our GitHub repository.
+
+**Q: Will this work with my preferred programming language?**
+A: Yes! The general metacoding template (set of instructions) works with any language supported by GitHub Copilot.
+
+**Q: Can I customize the workflow for my team's needs?**
+A: Absolutely! All instruction files can be modified to match your team's specific requirements.
+
+**Q: Does this replace learning to code?**
+A: No, it enhances your learning by providing guidance on proven practices while you develop your coding skills.
+
+**Q: What VS Code settings are required?**
+A: The CLI automatically configures required settings, but you need `github.copilot.chat.codeGeneration.useInstructionFiles: true` and `chat.promptFiles: true`.
+
+## Troubleshooting
+
+**Installation Issues:**
+
+- Make sure Node.js (version 16+) is installed: `node --version`
+- Verify npm is working: `npm --version`
+- Try clearing npm cache: `npm cache clean --force`
+
+**GitHub Copilot not responding to instructions:**
+
+- Make sure you've restarted VS Code after installation
+- Verify your GitHub Copilot subscription is active
+- Check that the instruction files are in the correct `.github/` folder
+- Ensure VS Code settings include the required custom instruction settings
+
+**Instructions not applying automatically:**
+
+- Ensure file names match exactly (including the `.instructions.md` extension)
+- Verify the folder structure is correct
+- Try manually referencing instructions in GitHub Copilot
+- Run `metacoding validate` to check your setup
+
+**CLI Command Issues:**
+
+- Ensure metacoding is installed globally: `npm list -g metacoding`
+- Try reinstalling: `npm uninstall -g metacoding && npm install -g metacoding`
+- Check PATH configuration if command not found
+
+## Official Resources
+
+Learn more about GitHub Copilot custom instructions:
+
+- **[VS Code Custom Instructions Guide](https://code.visualstudio.com/blogs/2025/03/26/custom-instructions)** - **Official comprehensive guide** from the VS Code team on custom instructions
+- **[GitHub Copilot Documentation](https://docs.github.com/en/copilot/using-github-copilot/best-practices-for-using-github-copilot)** - Official GitHub Copilot best practices
+- **[VS Code Copilot Customization](https://code.visualstudio.com/docs/copilot/copilot-customization)** - Technical documentation for advanced customization
+
+## 🤝 Contributing
+
+We welcome contributions to make metacoding even better! Whether you have:
+
+- Improvements to existing workflows
+- New instruction patterns for specific technologies
+- Documentation enhancements
+- Bug fixes or clarifications
+
+Feel free to open an issue or submit a pull request.
+
+## 📄 License
+
+This project is open source and available under the [MIT License](https://opensource.org/licenses/MIT). Use it freely in personal or commercial projects.

package/bin/metacoding.js

@@ -0,0 +1,27 @@
+#!/usr/bin/env node
+
+/**
+ * metacoding CLI Entry Point
+ *
+ * This file serves as the main entry point for the metacoding CLI tool.
+ * It delegates to the compiled TypeScript code in the lib directory.
+ */
+
+const { main } = require('../lib/cli');
+
+// Handle uncaught exceptions gracefully
+process.on('uncaughtException', (error) => {
+  console.error('Unexpected error:', error.message);
+  process.exit(1);
+});
+
+process.on('unhandledRejection', (reason) => {
+  console.error('Unhandled promise rejection:', reason);
+  process.exit(1);
+});
+
+// Run the main CLI function
+main().catch((error) => {
+  console.error('CLI Error:', error.message);
+  process.exit(1);
+});

package/lib/cli.d.ts

@@ -0,0 +1,2 @@
+export declare function main(): Promise<void>;
+//# sourceMappingURL=cli.d.ts.map

package/lib/cli.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"cli.d.ts","sourceRoot":"","sources":["../src/cli.ts"],"names":[],"mappings":"AAWA,wBAAsB,IAAI,IAAI,OAAO,CAAC,IAAI,CAAC,CA4F1C"}

package/lib/cli.js

@@ -0,0 +1,83 @@
+"use strict";
+var __importDefault = (this && this.__importDefault) || function (mod) {
+    return (mod && mod.__esModule) ? mod : { "default": mod };
+};
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.main = main;
+const commander_1 = require("commander");
+const chalk_1 = __importDefault(require("chalk"));
+const init_1 = require("./commands/init");
+const validate_1 = require("./commands/validate");
+const update_1 = require("./commands/update");
+const packageJson = require('../package.json');
+const version = packageJson.version;
+async function main() {
+    const program = new commander_1.Command();
+    program
+        .name('metacoding')
+        .description('Guided Development Workflow for GitHub Copilot')
+        .version(version)
+        .addHelpText('after', `
+${chalk_1.default.cyan('Examples:')}
+  ${chalk_1.default.dim('$')} metacoding init                    # Initialize metacoding in current directory
+  ${chalk_1.default.dim('$')} metacoding init --template react   # Initialize with React template
+  ${chalk_1.default.dim('$')} metacoding validate                # Validate current metacoding setup
+  ${chalk_1.default.dim('$')} metacoding update                  # Update to latest metacoding version
+
+${chalk_1.default.cyan('Learn more:')}
+  Documentation: https://github.com/anton-g-kulikov/metacoding
+  Issues: https://github.com/anton-g-kulikov/metacoding/issues
+    `);
+    program
+        .command('init')
+        .description('Initialize metacoding in the current project')
+        .option('-t, --template <type>', 'project template (general, react, node, python)', 'general')
+        .option('-f, --force', 'overwrite existing files without confirmation')
+        .option('--skip-vscode', 'skip VS Code settings configuration')
+        .option('--skip-git', 'skip Git repository initialization check')
+        .action(async (options) => {
+        try {
+            const initCommand = new init_1.InitCommand();
+            await initCommand.execute(options);
+        }
+        catch (error) {
+            console.error(chalk_1.default.red('Error during initialization:'), error instanceof Error ? error.message : error);
+            process.exit(1);
+        }
+    });
+    program
+        .command('validate')
+        .description('Validate current metacoding setup')
+        .option('--fix', 'automatically fix issues where possible')
+        .option('--strict', 'use strict validation rules')
+        .action(async (options) => {
+        try {
+            const validateCommand = new validate_1.ValidateCommand();
+            await validateCommand.execute(options);
+        }
+        catch (error) {
+            console.error(chalk_1.default.red('Error during validation:'), error instanceof Error ? error.message : error);
+            process.exit(1);
+        }
+    });
+    program
+        .command('update')
+        .description('Update existing metacoding setup to latest version')
+        .option('--template <type>', 'update to specific template type')
+        .option('--backup', 'create backup of existing files before updating')
+        .action(async (options) => {
+        try {
+            const updateCommand = new update_1.UpdateCommand();
+            await updateCommand.execute(options);
+        }
+        catch (error) {
+            console.error(chalk_1.default.red('Error during update:'), error instanceof Error ? error.message : error);
+            process.exit(1);
+        }
+    });
+    if (process.argv.length <= 2) {
+        program.help();
+    }
+    await program.parseAsync(process.argv);
+}
+//# sourceMappingURL=cli.js.map

package/lib/cli.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"cli.js","sourceRoot":"","sources":["../src/cli.ts"],"names":[],"mappings":";;;;;AAWA,oBA4FC;AAvGD,yCAAoC;AACpC,kDAA0B;AAC1B,0CAA8C;AAC9C,kDAAsD;AACtD,8CAAkD;AAClD,MAAM,WAAW,GAAG,OAAO,CAAC,iBAAiB,CAAC,CAAC;AAC/C,MAAM,OAAO,GAAG,WAAW,CAAC,OAAO,CAAC;AAK7B,KAAK,UAAU,IAAI;IACxB,MAAM,OAAO,GAAG,IAAI,mBAAO,EAAE,CAAC;IAE9B,OAAO;SACJ,IAAI,CAAC,YAAY,CAAC;SAClB,WAAW,CAAC,gDAAgD,CAAC;SAC7D,OAAO,CAAC,OAAO,CAAC;SAChB,WAAW,CACV,OAAO,EACP;EACJ,eAAK,CAAC,IAAI,CAAC,WAAW,CAAC;IACrB,eAAK,CAAC,GAAG,CAAC,GAAG,CAAC;IACd,eAAK,CAAC,GAAG,CAAC,GAAG,CAAC;IACd,eAAK,CAAC,GAAG,CAAC,GAAG,CAAC;IACd,eAAK,CAAC,GAAG,CAAC,GAAG,CAAC;;EAEhB,eAAK,CAAC,IAAI,CAAC,aAAa,CAAC;;;KAGtB,CACA,CAAC;IAGJ,OAAO;SACJ,OAAO,CAAC,MAAM,CAAC;SACf,WAAW,CAAC,8CAA8C,CAAC;SAC3D,MAAM,CACL,uBAAuB,EACvB,iDAAiD,EACjD,SAAS,CACV;SACA,MAAM,CAAC,aAAa,EAAE,+CAA+C,CAAC;SACtE,MAAM,CAAC,eAAe,EAAE,qCAAqC,CAAC;SAC9D,MAAM,CAAC,YAAY,EAAE,0CAA0C,CAAC;SAChE,MAAM,CAAC,KAAK,EAAE,OAAO,EAAE,EAAE;QACxB,IAAI,CAAC;YACH,MAAM,WAAW,GAAG,IAAI,kBAAW,EAAE,CAAC;YACtC,MAAM,WAAW,CAAC,OAAO,CAAC,OAAO,CAAC,CAAC;QACrC,CAAC;QAAC,OAAO,KAAK,EAAE,CAAC;YACf,OAAO,CAAC,KAAK,CACX,eAAK,CAAC,GAAG,CAAC,8BAA8B,CAAC,EACzC,KAAK,YAAY,KAAK,CAAC,CAAC,CAAC,KAAK,CAAC,OAAO,CAAC,CAAC,CAAC,KAAK,CAC/C,CAAC;YACF,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;QAClB,CAAC;IACH,CAAC,CAAC,CAAC;IAGL,OAAO;SACJ,OAAO,CAAC,UAAU,CAAC;SACnB,WAAW,CAAC,mCAAmC,CAAC;SAChD,MAAM,CAAC,OAAO,EAAE,yCAAyC,CAAC;SAC1D,MAAM,CAAC,UAAU,EAAE,6BAA6B,CAAC;SACjD,MAAM,CAAC,KAAK,EAAE,OAAO,EAAE,EAAE;QACxB,IAAI,CAAC;YACH,MAAM,eAAe,GAAG,IAAI,0BAAe,EAAE,CAAC;YAC9C,MAAM,eAAe,CAAC,OAAO,CAAC,OAAO,CAAC,CAAC;QACzC,CAAC;QAAC,OAAO,KAAK,EAAE,CAAC;YACf,OAAO,CAAC,KAAK,CACX,eAAK,CAAC,GAAG,CAAC,0BAA0B,CAAC,EACrC,KAAK,YAAY,KAAK,CAAC,CAAC,CAAC,KAAK,CAAC,OAAO,CAAC,CAAC,CAAC,KAAK,CAC/C,CAAC;YACF,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;QAClB,CAAC;IACH,CAAC,CAAC,CAAC;IAGL,OAAO;SACJ,OAAO,CAAC,QAAQ,CAAC;SACjB,WAAW,CAAC,oDAAoD,CAAC;SACjE,MAAM,CAAC,mBAAmB,EAAE,kCAAkC,CAAC;SAC/D,MAAM,CAAC,UAAU,EAAE,iDAAiD,CAAC;SACrE,MAAM,CAAC,KAAK,EAAE,OAAO,EAAE,EAAE;QACxB,IAAI,CAAC;YACH,MAAM,aAAa,GAAG,IAAI,sBAAa,EAAE,CAAC;YAC1C,MAAM,aAAa,CAAC,OAAO,CAAC,OAAO,CAAC,CAAC;QACvC,CAAC;QAAC,OAAO,KAAK,EAAE,CAAC;YACf,OAAO,CAAC,KAAK,CACX,eAAK,CAAC,GAAG,CAAC,sBAAsB,CAAC,EACjC,KAAK,YAAY,KAAK,CAAC,CAAC,CAAC,KAAK,CAAC,OAAO,CAAC,CAAC,CAAC,KAAK,CAC/C,CAAC;YACF,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;QAClB,CAAC;IACH,CAAC,CAAC,CAAC;IAGL,IAAI,OAAO,CAAC,IAAI,CAAC,MAAM,IAAI,CAAC,EAAE,CAAC;QAC7B,OAAO,CAAC,IAAI,EAAE,CAAC;IACjB,CAAC;IAGD,MAAM,OAAO,CAAC,UAAU,CAAC,OAAO,CAAC,IAAI,CAAC,CAAC;AACzC,CAAC"}

package/lib/commands/init.d.ts

@@ -0,0 +1,15 @@
+import { InitOptions } from '../types';
+export declare class InitCommand {
+    private templateManager;
+    private fileSystem;
+    private vscodeService;
+    private projectDetector;
+    constructor();
+    execute(options: InitOptions): Promise<void>;
+    private getProjectConfiguration;
+    private setupProject;
+    private getDefaultTestFramework;
+    private getDefaultBuildTool;
+    private displayNextSteps;
+}
+//# sourceMappingURL=init.d.ts.map

package/lib/commands/init.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"init.d.ts","sourceRoot":"","sources":["../../src/commands/init.ts"],"names":[],"mappings":"AAGA,OAAO,EAAE,WAAW,EAAiB,MAAM,UAAU,CAAC;AAStD,qBAAa,WAAW;IACtB,OAAO,CAAC,eAAe,CAAkB;IACzC,OAAO,CAAC,UAAU,CAAoB;IACtC,OAAO,CAAC,aAAa,CAAgB;IACrC,OAAO,CAAC,eAAe,CAAkB;;IAYnC,OAAO,CAAC,OAAO,EAAE,WAAW,GAAG,OAAO,CAAC,IAAI,CAAC;YAqCpC,uBAAuB;YAgGvB,YAAY;IAyC1B,OAAO,CAAC,uBAAuB;IAgB/B,OAAO,CAAC,mBAAmB;IAgB3B,OAAO,CAAC,gBAAgB;CAezB"}