@l4yercak3/cli 1.0.0

package/.claude/settings.local.json

@@ -0,0 +1,18 @@
+{
+  "permissions": {
+    "allow": [
+      "Bash(npm run lint:*)",
+      "Bash(npm test:*)",
+      "Bash(npm run verify:*)",
+      "Bash(find:*)",
+      "Bash(node bin/cli.js:*)",
+      "Bash(npm install:*)",
+      "Bash(npm run test:coverage:*)",
+      "Bash(git init:*)",
+      "Bash(git add:*)",
+      "Bash(git commit:*)",
+      "Bash(gh repo create:*)",
+      "Bash(npm whoami:*)"
+    ]
+  }
+}

package/.cursor/rules.md

@@ -0,0 +1,203 @@
+# L4YERCAK3 CLI Tool - Development Rules
+
+This document defines the coding standards, quality checks, and development practices for the L4YERCAK3 CLI tool.
+
+## Quality Assurance Checklist
+
+Every code change must pass these checks before being considered complete:
+
+### 1. Type Checking ✅
+- **Command**: `npm run type-check`
+- **Requirement**: All TypeScript/JavaScript code must pass type checking
+- **Action**: Fix all type errors before committing
+
+### 2. Linting ✅
+- **Command**: `npm run lint`
+- **Requirement**: Code must pass ESLint without errors
+- **Action**: Fix all linting errors or disable rules with justification
+
+### 3. Production Build ✅
+- **Command**: `npm run build`
+- **Requirement**: Package must build successfully for production
+- **Action**: Ensure all dependencies are properly declared
+
+### 4. Testing ✅
+- **Command**: `npm test`
+- **Requirement**: All tests must pass
+- **Action**: Add tests for new features, fix failing tests
+
+## Development Workflow
+
+### Before Committing
+1. Run `npm run verify` (runs all checks)
+2. Ensure all checks pass
+3. Review changes
+4. Commit with descriptive message
+
+### After Major Changes
+1. Run full verification suite
+2. Test CLI locally with `npm link`
+3. Test with example projects
+4. Update documentation if needed
+
+## Code Standards
+
+### JavaScript/Node.js
+- Use CommonJS (require/module.exports) for compatibility
+- Follow Node.js best practices
+- Use async/await for asynchronous operations
+- Handle errors properly with try/catch
+
+### File Structure
+- Keep files modular and focused
+- Use descriptive file names
+- Group related functionality together
+- Document complex logic
+
+### Error Handling
+- Always handle errors gracefully
+- Provide helpful error messages
+- Log errors appropriately
+- Don't expose sensitive information
+
+### Code Style
+- Use consistent indentation (2 spaces)
+- Use meaningful variable names
+- Keep functions small and focused
+- Add comments for complex logic
+
+## Architecture Principles
+
+### Modularity
+- Keep commands separate from generators
+- Separate concerns (detection, generation, configuration)
+- Make code reusable across commands
+
+### User Experience
+- Provide clear, helpful error messages
+- Show progress indicators for long operations
+- Use colors and formatting for better readability
+- Guide users through setup process
+
+### Maintainability
+- Write self-documenting code
+- Add JSDoc comments for public APIs
+- Keep dependencies minimal
+- Update dependencies regularly
+
+## Dependencies
+
+### Current Dependencies
+- `chalk@^4.1.2` - Terminal colors (v4 for CommonJS compatibility)
+- `figlet@^1.7.0` - ASCII art generation
+
+### Adding New Dependencies
+- Prefer lightweight, well-maintained packages
+- Check bundle size impact
+- Ensure CommonJS compatibility
+- Document why dependency is needed
+
+## Testing Strategy
+
+### Unit Tests
+- Test individual functions
+- Mock external dependencies
+- Test error cases
+- Test edge cases
+
+### Integration Tests
+- Test CLI commands end-to-end
+- Test with real project structures
+- Test error scenarios
+- Test with different Node.js versions
+
+## Documentation
+
+### Code Documentation
+- Add JSDoc comments for all public functions
+- Document complex algorithms
+- Explain non-obvious code
+
+### User Documentation
+- Keep README.md up to date
+- Document all commands
+- Provide examples
+- Include troubleshooting section
+
+## Version Management
+
+### Semantic Versioning
+- `MAJOR.MINOR.PATCH`
+- Major: Breaking changes
+- Minor: New features (backward compatible)
+- Patch: Bug fixes
+
+### Before Publishing
+1. Update version in package.json
+2. Update CHANGELOG.md
+3. Run full test suite
+4. Test installation via npm
+
+## Security
+
+### Sensitive Data
+- Never commit API keys or secrets
+- Use environment variables for configuration
+- Validate user input
+- Sanitize file paths
+
+### Dependencies
+- Keep dependencies up to date
+- Check for security vulnerabilities: `npm audit`
+- Review dependency changes
+
+## Performance
+
+### CLI Performance
+- Minimize startup time
+- Use lazy loading where appropriate
+- Cache expensive operations
+- Optimize file I/O
+
+## Compatibility
+
+### Node.js Versions
+- Support Node.js 14+ (as specified in package.json)
+- Test on multiple Node.js versions
+- Use features available in minimum version
+
+### Operating Systems
+- Test on macOS, Linux, Windows
+- Handle path differences
+- Test file permissions
+
+## Git Workflow
+
+### Commit Messages
+- Use descriptive commit messages
+- Reference issues when applicable
+- Keep commits focused and atomic
+
+### Branching
+- Use feature branches for new features
+- Keep main branch stable
+- Use descriptive branch names
+
+## Continuous Improvement
+
+### Code Review
+- Review all changes before merging
+- Look for potential bugs
+- Suggest improvements
+- Ensure standards are followed
+
+### Refactoring
+- Refactor when code becomes complex
+- Improve based on usage patterns
+- Keep code maintainable
+- Don't refactor working code unnecessarily
+
+---
+
+**Remember**: Quality over speed. Take time to write clean, maintainable code that others (and future you) will appreciate.
+

package/.eslintrc.js

@@ -0,0 +1,31 @@
+module.exports = {
+  env: {
+    node: true,
+    es2021: true,
+  },
+  extends: ['eslint:recommended'],
+  parserOptions: {
+    ecmaVersion: 2021,
+    sourceType: 'module',
+  },
+  rules: {
+    'no-console': 'off', // CLI tools need console output
+    'no-unused-vars': ['warn', { argsIgnorePattern: '^_' }],
+    'no-undef': 'error',
+    'prefer-const': 'warn',
+    'no-var': 'warn',
+    'prefer-arrow-callback': 'warn',
+    'arrow-body-style': ['warn', 'as-needed'],
+    'object-shorthand': 'warn',
+    'prefer-template': 'warn',
+  },
+  overrides: [
+    {
+      files: ['tests/**/*.js'],
+      env: {
+        jest: true,
+      },
+    },
+  ],
+};
+

package/README.md

@@ -0,0 +1,227 @@
+# 🍰 Icing on the L4yercak3
+
+**The sweet finishing touch for your Layer Cake integration**
+
+A beautiful CLI tool for setting up external projects that integrate with the Layer Cake platform.
+
+## 🎨 Features
+
+- ✨ Beautiful ASCII art logo with 3D font and rainbow gradient
+- 🏗️ Visual building/plumbing metaphor
+- 🎨 Colorful terminal output
+- 🚀 Easy project setup
+
+## 📦 Installation
+
+```bash
+npm install -g @l4yercak3/cli
+```
+
+Or use with npx:
+
+```bash
+npx @l4yercak3/cli
+```
+
+## 🚀 Usage
+
+### Quick Start
+
+```bash
+# Show logo and welcome message
+npx @l4yercak3/cli
+
+# Or if installed globally
+l4yercak3
+# or use the alias
+icing
+```
+
+### Commands (Coming Soon)
+
+```bash
+# Initialize a new project
+npx @l4yercak3/cli spread
+
+# Show help
+npx @l4yercak3/cli --help
+
+# Show version
+npx @l4yercak3/cli --version
+```
+
+### Bin Commands
+
+The package exposes two bin commands (both point to the same CLI):
+- `l4yercak3` - Main command name
+- `icing` - Alias (short for "icing on the l4yercak3")
+
+## 🏗️ The Metaphor
+
+**l4yercak3 = The Plumbing/Foundation**
+- Database, Auth, Payments, CRM, Workflows
+- Lives in the basement/cellar
+- One platform powering everything
+
+**External Projects = The Floors**
+- Landing pages, client portals, mobile apps
+- Each floor built on the same foundation
+- Connect via API layer (plumbing pipes)
+
+**icing = The CLI Tool**
+- Automates the connection
+- "Spreads" the integration smoothly
+- The sweet finishing touch!
+
+## 🎨 Logo
+
+The logo uses:
+- **Font**: 3D-ASCII (from figlet)
+- **Colors**: Rainbow gradient
+- **Style**: Colorful, eye-catching, professional
+
+## 📝 Development
+
+### Package Location
+The package is located at: `~/Development/l4yercak3-cli`
+
+### Package Structure
+```
+l4yercak3-cli/
+├── bin/
+│   └── cli.js          # CLI entry point (executable)
+├── src/
+│   └── logo.js         # Logo display module (3D-ASCII font, rainbow gradient)
+├── package.json         # npm package config
+├── README.md           # This file
+└── .gitignore          # Git ignore file
+```
+
+### Local Development
+
+```bash
+# Navigate to package directory
+cd ~/Development/l4yercak3-cli
+
+# Install dependencies
+npm install
+
+# Run locally
+npm start
+# or
+node bin/cli.js
+
+# Test it locally (link globally for testing)
+npm link
+l4yercak3
+# or use the alias
+icing
+```
+
+### Logo Details
+
+The logo uses **VERSION 6** from the demo files:
+- **Font**: `3D-ASCII` (from figlet)
+- **Colors**: Rainbow gradient (`#FF1493` → `#FF69B4` → `#FF00FF` → `#9F7AEA` → `#8B5CF6` → `#3B82F6` → `#00BFFF` → `#10B981` → `#F59E0B` → `#EF4444` → `#FF6B6B`)
+- **Style**: Colorful, eye-catching, professional
+- **Metaphor**: Includes building/plumbing visualization below the logo
+
+### Publishing to npm
+
+When ready to publish:
+
+```bash
+# Navigate to package directory
+cd ~/Development/l4yercak3-cli
+
+# Login to npm (if not already logged in)
+npm login
+
+# Publish (make sure version is updated in package.json first)
+npm publish --access public
+
+# After publishing, users can install with:
+npm install -g @l4yercak3/cli
+
+# Or use with npx (no install needed):
+npx @l4yercak3/cli
+```
+
+### Version Management
+
+Before publishing, update the version in `package.json`:
+- Patch: `npm version patch` (1.0.0 → 1.0.1)
+- Minor: `npm version minor` (1.0.0 → 1.1.0)
+- Major: `npm version major` (1.0.0 → 2.0.0)
+
+### Next Steps / TODO
+
+- [ ] Add CLI commands (spread, login, etc.)
+- [ ] Add interactive questionnaire for project setup
+- [ ] Add OAuth credential generation
+- [ ] Add environment file generation
+- [ ] Add API client template generation
+- [ ] Add webhook handler templates
+- [ ] Add Stripe integration setup
+- [ ] Add School/CRM integration setup
+- [ ] Add project templates (landing page, portal, app)
+- [ ] Add help command with examples
+- [ ] Add update checker
+- [ ] Add telemetry (opt-in)
+
+### Related Files
+
+The logo demo files are located at:
+- `vc83-com/.kiro/npm_l4yercak3_tool/demo-logo-figlet-building.js` - All font variations
+- `vc83-com/.kiro/npm_l4yercak3_tool/demo-logo-plumbing-building.js` - Building metaphor versions
+- `vc83-com/.kiro/npm_l4yercak3_tool/PROJECT_VISION.md` - Full project vision and roadmap
+
+## 📄 License
+
+MIT
+
+## 🔧 Dependencies
+
+- **chalk@^4.1.2** - Terminal colors (v4 for CommonJS compatibility)
+- **figlet@^1.7.0** - ASCII art generation
+
+**Note**: We use chalk v4 (not v5) because v5 is ESM-only and this package uses CommonJS.
+
+## 🐛 Troubleshooting
+
+### Command not found after npm link
+
+If `l4yercak3` or `icing` commands aren't found after `npm link`:
+1. Check that `bin/cli.js` has executable permissions: `chmod +x bin/cli.js`
+2. Verify npm bin path: `npm bin -g`
+3. Make sure npm bin is in your PATH
+4. Try: `npm unlink` then `npm link` again
+
+### Colors not showing
+
+If colors don't appear in your terminal:
+- Make sure your terminal supports ANSI colors
+- Try setting `FORCE_COLOR=1` environment variable
+- Check terminal color settings
+
+### figlet font not found
+
+If you get a font error:
+- Make sure figlet is installed: `npm install figlet`
+- The font `3D-ASCII` should be included with figlet
+- Try listing available fonts: `figlet -l` (if figlet CLI is installed)
+
+## 🙏 Credits
+
+Built with:
+- [figlet](https://github.com/patorjk/figlet.js) - ASCII art generation
+- [chalk](https://github.com/chalk/chalk) - Terminal colors
+
+## 📚 Related Documentation
+
+- See `PROJECT_VISION.md` in `vc83-com/.kiro/npm_l4yercak3_tool/` for full project vision
+- See demo files in `vc83-com/.kiro/npm_l4yercak3_tool/` for logo variations
+
+---
+
+**🍰 Icing on the L4yercak3 - Build your floors on our foundation! 🍰**

package/bin/cli.js

@@ -0,0 +1,61 @@
+#!/usr/bin/env node
+
+/**
+ * CLI Entry Point
+ * Icing on the L4yercak3 - The sweet finishing touch for your Layer Cake integration
+ */
+
+const { Command } = require('commander');
+const { showLogo } = require('../src/logo');
+const chalk = require('chalk');
+
+// Import commands
+const loginCommand = require('../src/commands/login');
+const logoutCommand = require('../src/commands/logout');
+const statusCommand = require('../src/commands/status');
+const spreadCommand = require('../src/commands/spread');
+
+// Create CLI program
+const program = new Command();
+
+program
+  .name('l4yercak3')
+  .description('Icing on the L4yercak3 - The sweet finishing touch for your Layer Cake integration')
+  .version(require('../package.json').version);
+
+// Register commands
+program
+  .command(loginCommand.command)
+  .description(loginCommand.description)
+  .action(loginCommand.handler);
+
+program
+  .command(logoutCommand.command)
+  .description(logoutCommand.description)
+  .action(logoutCommand.handler);
+
+program
+  .command('auth')
+  .description('Authentication commands')
+  .addCommand(
+    new Command('status')
+      .description(statusCommand.description)
+      .action(statusCommand.handler)
+  );
+
+program
+  .command(spreadCommand.command)
+  .description(spreadCommand.description)
+  .action(spreadCommand.handler);
+
+// Show logo and welcome message if no command provided
+if (process.argv.length === 2) {
+  console.log(''); // initial spacing
+  showLogo(true);
+  console.log(chalk.bold.hex('#9F7AEA')('  🍰 Welcome to Icing on the L4yercak3! 🍰\n'));
+  console.log(chalk.gray('  The sweet finishing touch for your Layer Cake integration\n'));
+  program.help();
+}
+
+// Parse arguments
+program.parse(process.argv);

package/docs/ADDING_NEW_PROJECT_TYPE.md

@@ -0,0 +1,156 @@
+# Adding a New Project Type
+
+Quick guide for adding support for new frameworks (React, Vue, Svelte, etc.)
+
+## Quick Start
+
+### 1. Create Detector File
+
+Create `src/detectors/react-detector.js` (example for React):
+
+```javascript
+const BaseDetector = require('./base-detector');
+const fs = require('fs');
+const path = require('path');
+
+class ReactDetector extends BaseDetector {
+  get name() {
+    return 'react';
+  }
+
+  get priority() {
+    return 50; // Lower than Next.js (100)
+  }
+
+  detect(projectPath = process.cwd()) {
+    // Check for React-specific files
+    const packageJsonPath = path.join(projectPath, 'package.json');
+    if (!fs.existsSync(packageJsonPath)) {
+      return { detected: false, confidence: 0, metadata: {} };
+    }
+
+    try {
+      const packageJson = JSON.parse(fs.readFileSync(packageJsonPath, 'utf8'));
+      const deps = { ...packageJson.dependencies, ...packageJson.devDependencies };
+      
+      const hasReact = !!deps.react;
+      const hasTypeScript = !!deps.typescript || fs.existsSync(path.join(projectPath, 'tsconfig.json'));
+
+      if (!hasReact) {
+        return { detected: false, confidence: 0, metadata: {} };
+      }
+
+      return {
+        detected: true,
+        confidence: 0.9,
+        metadata: {
+          version: deps.react,
+          hasTypeScript,
+        },
+      };
+    } catch (error) {
+      return { detected: false, confidence: 0, metadata: {} };
+    }
+  }
+
+  getSupportedFeatures() {
+    return {
+      oauth: 'manual',  // No NextAuth, manual setup only
+      stripe: true,
+      crm: true,
+      projects: true,
+      invoices: true,
+    };
+  }
+
+  getAvailableGenerators() {
+    return [
+      'api-client',  // Shared generator
+      'env',          // Shared generator
+      // Add React-specific generators here if needed
+    ];
+  }
+}
+
+module.exports = new ReactDetector();
+```
+
+### 2. Register Detector
+
+Add to `src/detectors/registry.js`:
+
+```javascript
+const nextJsDetector = require('./nextjs-detector');
+const reactDetector = require('./react-detector');  // Add this
+
+const detectors = [
+  nextJsDetector,
+  reactDetector,  // Add this
+];
+```
+
+### 3. Test
+
+```bash
+cd /path/to/react/project
+l4yercak3 spread
+```
+
+You should see:
+```
+✅ Detected react project
+```
+
+---
+
+## What Gets Generated?
+
+### Shared Generators (Work for All Frameworks)
+
+- **`api-client`** - Generates API client (framework-agnostic)
+- **`env`** - Generates `.env.local.example` (framework-agnostic)
+
+### Framework-Specific Generators
+
+- **Next.js**: `nextauth` (NextAuth.js setup)
+- **React**: (none yet, but can add `react-auth` generator)
+- **Vue**: (none yet, but can add `vue-auth` generator)
+
+---
+
+## Feature Support Matrix
+
+When implementing `getSupportedFeatures()`, use:
+
+- `true` - Full support (e.g., Next.js OAuth with NextAuth.js)
+- `'manual'` - Guide only (e.g., React OAuth setup guide)
+- `false` - Not supported
+
+---
+
+## Priority Guidelines
+
+Set detector priority based on specificity:
+
+- **100**: Very specific (Next.js, Nuxt, SvelteKit)
+- **75**: Framework + build tool (Vite + React, Webpack + Vue)
+- **50**: Pure framework (React, Vue, Svelte)
+- **25**: Generic (JavaScript/TypeScript)
+
+Higher priority detectors run first. First match with confidence > 0.8 wins.
+
+---
+
+## Example: Adding Vue Support
+
+1. Create `src/detectors/vue-detector.js`
+2. Register in `registry.js`
+3. Test with a Vue project
+4. Add Vue-specific generators if needed (e.g., `vue-auth-generator.js`)
+
+That's it! The architecture handles the rest automatically.
+
+---
+
+**See:** `DETECTOR_ARCHITECTURE.md` for full architecture details
+