same layout and the same
semantics.
## Development
### Commands
- Python lives in `python/` (`mirage/`, `tests/`). Setup:
`cd python && uv sync --all-extras --no-extra camel`. Add dependencies with
`uv add`. Test
scheduledTime`, `platformSettings` on a draft or scheduled post), and
`DELETE /delete-post/ `. Also `post-logs`, `test-connection`,
`platform-limits` and `webhooks`. Prefer editing a scheduled post over
delete-and-recreate.
- **Image
compiled server
- Dev: `pnpm run dev` - Runs server with tsx (no compilation needed)
- Test: `pnpm test` - Run all tests
- Test Watch: `pnpm test:watch` - Run tests in watch mode
- Integration
development mode)
./gradlew :app:webApp:wasmJsBrowserDevelopmentRun
# Run backend server
./gradlew :backend:run
# Run backend tests
./gradlew :backend:test
# Run shared module tests (JVM target)
./gradlew :app:shared:jvmTest
# Run core
embed step!
cd web && npm run build && cd .. && go build -o radar ./cmd/explorer
```
### Build / test / run
`make help` lists every target — read the Makefile when uncertain
Code** - Never use emoji characters in any code, comments, or string literals
2. **Test Coverage** - All new features must have unit test coverage of at least 80%
3. **i18n Required
Debug, Release, DebugAll, ReleaseAll, Debug462, Debug70)
dotnet build src/Microsoft.PowerFx.sln -p:Configuration=Release
# Run all tests
dotnet test src/Microsoft.PowerFx.sln
# Run tests for a specific project
dotnet test src/tests/Microsoft.PowerFx.Core.Tests.Shared/Microsoft.PowerFx.Core.Tests.Shared.csproj
# Run a single
Windows
# Default configuration is DebugAll if not specified
# Output packages go to src/outputpackages/
```
### Running Tests
```bash
# From src/ directory
.\runLocalTests.cmd [Configuration] # Windows (uses VSTest)
# Or using dotnet CLI (from solution
single source of truth for engineering rules:
- Follow [`../AGENTS.md`](../AGENTS.md) for all workflow, testing, and review requirements.
Skill layout for multi-agent compatibility:
- Canonical skills directory: `.agents/skills/`
- Claude compatibility path
structures
## Development Commands
### Core Development Tasks
```bash
# Install dependencies
uv sync --all-extras
# Run tests (use these specific commands)
make test # Standard test suite (offline only)
make test-fuzz
published package changed.
**Ponytail skill (mandatory).** Before planning, writing, or editing application code, tests, or examples, load `.claude/skills/ponytail/SKILL.md` and follow it. Do not design or implement without it. Ponytail does
PentestAgent — CLAUDE.md
## Project overview
**PentestAgent** (v0.2.0) is an AI-powered penetration testing framework built in Python.
It wraps LiteLLM to support any provider (Anthropic, OpenAI, etc.) and exposes
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
Where does it go?
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
What should it contain?
Build and test commands, the project's layout, conventions that aren't obvious from the code, and mistakes to avoid. Short files tend to work better than long ones.
CLAUDE.md or AGENTS.md?
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.