|
| 1 | +# CLAUDE.md |
| 2 | + |
| 3 | +This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository. |
| 4 | + |
| 5 | +## Overview |
| 6 | + |
| 7 | +This repository contains a single-page React application for creating devfiles through a user-friendly GUI wizard. The application uses React and Tailwind CSS to provide a step-by-step interface for generating devfile 2.3.0 compliant YAML files. |
| 8 | + |
| 9 | +**Key Resources:** |
| 10 | +- Devfile specification: https://devfile.io/docs/ |
| 11 | +- Feature request: https://github.com/devfile/api/issues/1765 |
| 12 | +- Devfile 2.3.0 spec should be the target version |
| 13 | + |
| 14 | +## Project Architecture |
| 15 | + |
| 16 | +**Application Type:** Single-page application (SPA) with no backend or persistent state |
| 17 | +**UI Framework:** React |
| 18 | +**Styling:** Tailwind CSS |
| 19 | +**Output:** Generated devfile.yaml files available for download |
| 20 | + |
| 21 | +The application is stateless - all devfile generation happens client-side with no data persistence. |
| 22 | + |
| 23 | +## Development Commands |
| 24 | + |
| 25 | +This section will be populated once the project structure is initialized. Expected commands include: |
| 26 | +- `npm install` - Install dependencies |
| 27 | +- `npm run dev` - Start development server |
| 28 | +- `npm run build` - Build for production |
| 29 | +- `npm run lint` - Run linter |
| 30 | +- `npm run test` - Run tests (if applicable) |
| 31 | + |
| 32 | +## MCP Servers |
| 33 | + |
| 34 | +This project uses the following MCP servers (configured in `.mcp.json`): |
| 35 | + |
| 36 | +- **context7**: Provides up-to-date React and Tailwind CSS documentation |
| 37 | +- **playwright**: For browser automation and testing |
| 38 | + |
| 39 | +## Key Implementation Requirements |
| 40 | + |
| 41 | +1. **Step-by-step wizard interface** - Guide users through devfile creation with clear, sequential steps |
| 42 | +2. **Devfile 2.3.0 compliance** - Generated YAML must conform to the devfile 2.3.0 specification |
| 43 | +3. **Download capability** - Users must be able to download the generated devfile.yaml |
| 44 | +4. **Single page design** - All functionality contained in one web page with no routing |
| 45 | +5. **No state persistence** - Application does not save or persist user data between sessions |
| 46 | + |
| 47 | +## Devfile Concepts to Understand |
| 48 | + |
| 49 | +When working with this codebase, familiarize yourself with these devfile concepts: |
| 50 | +- Components (containers, volumes, kubernetes resources) |
| 51 | +- Commands (exec, apply, composite) |
| 52 | +- Events (preStart, postStart, preStop, postStop) |
| 53 | +- Projects (git repositories) |
| 54 | +- StarterProjects (templates) |
| 55 | +- Metadata (name, version, description, attributes) |
| 56 | + |
| 57 | +Refer to https://devfile.io/docs/ for detailed schema and examples. |
0 commit comments