Skip to content
Prompt

celo-composer — Windsurf Rules

by celo-org

AI Summary

celo-composer is a starter project with all code needed to build, deploy, and upgrade a dapps on Celo.

Install

Copy this and paste it into Claude Code, Cursor, or any AI assistant:

I want to add the "celo-composer — Windsurf Rules" prompt rules to my project.
Repository: https://github.com/celo-org/celo-composer

Please read the repo to find the rules/prompt file, then:
1. Download it to the correct location (.cursorrules, .windsurfrules, .github/prompts/, or project root — based on the file type)
2. If there's an existing rules file, merge the new rules in rather than overwriting
3. Confirm what was added

Description

celo-composer is a starter project with all code needed to build, deploy, and upgrade a dapps on Celo.

Project Overview

• This is a CLI tool that generates customizable Celo blockchain starter kits • The tool creates monorepo structures with dynamic template composition • Focus on modularity, code reusability, and developer experience • Always generate projects without docs folders unless explicitly requested

Tech Stack & Architecture

• Use Node.js with TypeScript for the CLI tool • Use Commander.js for CLI framework and Inquirer.js for interactive prompts • Use Turborepo for monorepo management in generated projects • Use shadcn/ui as the default UI library in all web templates • Use Plop.js for template generation and composition • Use PNPM as the package manager • Templates should use Next.js 14+ with App Router

Code Style & Standards

• Follow TypeScript strict mode - avoid any types • Use functional programming patterns, avoid classes where possible • Use descriptive variable names with auxiliary verbs (isLoading, hasError) • Prefer named exports over default exports • Use PascalCase for React components and interfaces • Use camelCase for functions and variables • Use kebab-case for file and directory names

Template Structure & Organization

• All templates must follow the shared monorepo structure with apps/ and packages/ • Base template should include shadcn/ui setup in packages/ui • Web apps should import components from @workspace/ui • Smart contract templates go in packages/contracts/ • Shared utilities go in packages/utils/ • Never create docs/ folders in generated projects

Discussion

0/2000
Loading comments...

Health Signals

MaintenanceCommitted 18d ago
Active
Adoption100+ stars on GitHub
188 ★ · Growing
DocsREADME + description
Well-documented

GitHub Signals

Stars188
Forks190
Issues20
Updated18d ago
View on GitHub
MIT License

My Fox Den

Community Rating

Sign in to rate this booster

Works With

Any AI assistant that accepts custom rules or system prompts

Claude
ChatGPT
Cursor
Windsurf
Copilot
+ more