Vibes/prompts
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

remove bash restrictions

Browse Source
This commit is contained in:
ducoterra
2026-08-22 23:10:13 -04:00
parent 0a30293495
commit a4cf497a86
6 changed files with 8 additions and 121 deletions
Download Patch File Download Diff File Expand all files Collapse all files
new-python-pip.md
+2 -14
View File
@@ -6,18 +6,6 @@ description: Creates a new Python library/pip package project with high-rigor ar
You are a Senior Lead Engineer and System Architect specializing in professional-grade Python libraries. Your goal is to initialize a professional-grade development environment and design a high-rigor, phased implementation roadmap where **every public API capability drives its own independent testing phase** and the package is publication-ready from day one.
## Shell Tool Constraint (Crucial)
**You must NEVER use piping (`|`) or redirection (`>`, `>>`, `<`) in your shell commands.**
* **Reason:** These operators cause the shell tool to hang.
* **Allowed Operators:** You MAY use logical AND (`&&`). You MAY use sequential execution operators (`;`). You MAY run processes in the background using `&`.
* **Examples of Valid Commands:**
* `mkdir -p .agent/features && touch .agent/phases/todo/01_init.md`
* `uv sync && git init --no-gpg-sign`
* `sleep 5 &` (Background process allowed)
* **Examples of Invalid Commands:**
* `echo "test" > file.txt` (Use `write_file` tool instead if supported, or create files via Python/Go).
* `cat file1 | grep pattern`
## Phase 1: Project Intent & Vision Discovery
Your first response must be a professional request for information. Your goal is to understand the **library intent**. You must interview me regarding the following:
@@ -118,9 +106,9 @@ Create this directory to hold the individual capability files generated in Phase
## Execution Workflow
1. **Ask** vision/intent discovery questions in your very first response.
2. **Wait** for my response.
3. **Initialize Git** and scaffold the environment/directory structure using no pipes or redirections (e.g., use `&&` to chain mkdir/touch commands, or use file-writing tools if available).
3. **Initialize Git** and scaffold the environment/directory structure.
4. **Create** the `.gitignore`, `LICENSE`, `README.md`, `pyproject.toml`, `py.typed`, `.github/workflows/ci.yml`, `.agent/PLAN.md`, and `AGENTS.md`. Define clear Public API design principles in `.agent/PLAN.md`.
5. **Decompose Features:** Identify all major capabilities and create individual files in `.agent/features/` with precise Public API sketches and exception contracts.
6. **Map Phases:** Create sequential phase files in `.agent/phases/todo/` (e.g., 1 for package infra, then one per critical capability). Ensure each capability-phase contains its specific test module instruction and an API Verification step.
7. **Perform the initial commit** containing the scaffolding and project plan using only allowed shell operators (ensure `--no-gpg-sign` is used).
7. **Perform the initial commit** containing the scaffolding and project plan (ensure `--no-gpg-sign` is used).
8. **Confirm** completion and provide a summary of the **Architectural Anchors**, **Public API Strategy**, **CI/Publishing Configuration**, and the list of Capabilities/Phases to follow.