Ricardo Carneiro
ea6cdb5395
- ASP.NET Core 9 Razor Pages + Minimal API hybrid - 14 validators (CPF, CEP, CNPJ, email, phone, name, yes-no, birthdate, handoff, cancel-intent, company-name, plate-br, postal-code, validate_reply) - OAuth login (Google, Microsoft, GitHub) + cookie auth - MongoDB usage tracking + CEP cache collection - Stripe checkout with inline PriceData (no Price IDs) - MCP server for Claude Code / Cursor integration - Playground (10 calls/IP/day, no auth) - Docs: Quickstart, API Reference, N8N, MCP, Créditos, Erros, Fluxos - Credit system: 3 cr standard validators, 5 cr validate_reply - SmartSuggestion: contextual re-ask via IA when obtained=false - Per-IP rate limiting + daily cap + shared-IP abuse detection - Lightbox for comic images - Validadores page split: Brasileiros / Universais + Em breve Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
41 lines
1.9 KiB
Markdown
41 lines
1.9 KiB
Markdown
# Project instructions
|
|
|
|
## ctx — use before reading files
|
|
|
|
This project has `ctx` available in PATH. Use it to understand the codebase **before** reading files directly. It produces compact markdown summaries that cost far fewer tokens than raw file content.
|
|
|
|
### When to use
|
|
|
|
**Always use `ctx` first** when you need to:
|
|
- Understand project structure → `ctx csharp project`
|
|
- Understand a file's structure → `ctx csharp outline <file>`
|
|
- Check build errors → `ctx csharp errors`
|
|
- Understand git state → `ctx git`
|
|
- Detect what stack this project uses → `ctx auto detect`
|
|
|
|
### Workflow
|
|
|
|
1. **Start of session:** run `ctx auto detect` to see what's here, then `ctx csharp project` for an overview.
|
|
2. **Before reading a file:** run `ctx csharp outline <file>` first. Only read the full file if the outline isn't enough (e.g., you need to see method body logic).
|
|
3. **After making changes:** run `ctx csharp errors` instead of `dotnet build` — the output is pre-filtered to only relevant diagnostics.
|
|
4. **Before committing:** run `ctx git` for a compact diff summary.
|
|
|
|
### Available commands
|
|
|
|
```
|
|
ctx auto detect # detect stack(s) in current directory
|
|
ctx auto project # run project summary for all detected stacks
|
|
|
|
ctx csharp project # .NET solution overview (projects, refs, packages)
|
|
ctx csharp outline <file.cs> # file structure without method bodies
|
|
ctx csharp errors # filtered dotnet build output (errors + top warnings)
|
|
|
|
ctx git # branch, status, recent commits, diff summary
|
|
```
|
|
|
|
### Important
|
|
|
|
- `ctx` output is a **summary**, not the full picture. If you need implementation details (method bodies, exact logic, specific lines), read the file directly.
|
|
- Do not run `ctx` commands that don't match the project stack. Use `ctx auto detect` if unsure.
|
|
- `ctx csharp errors` assumes `dotnet restore` was already run. If you get restore errors, run `dotnet restore` first, then `ctx csharp errors`.
|