fcoury

nanoclaw · AI Dev Team — Índice de Prompts

Todos os prompts usados pelo orchestrator (src/dev-team-orchestrator.ts), em ordem lógica de execução.

Variáveis em {{duplas chaves}} são substituídas em runtime pelo TypeScript.

---

⚙️ Setup (uma vez por instalação)

fcoury

My tmux Workflow

I use tmux as my daily terminal multiplexer. Over time I've built a small set of shell helpers and keybindings that make session management nearly frictionless — both locally and on remote machines.

The Core Idea

Every project gets its own tmux session, named after the directory. If I'm in ~/code/myapp, the session is called myapp. Dots get replaced with underscores so tmux doesn't complain (e.g. my.project becomes my_project). This convention means I never have to think about session names — the directory is the name.

Getting Into a Session

fcoury

# Add this snippet to ~/.vibe/config.toml

[[models]]
name = "mistralai/devstral-small-2507"
provider = "lmstudio"
alias = "lmstudio-local"
input_price = 0.0
output_price = 0.0

fcoury

#!/bin/bash

# Read the JSON input from stdin
input=$(cat)

# Extract the cwd from the JSON
if command -v jq &> /dev/null; then
    cwd=$(echo "$input" | jq -r '.cwd')
    # If cwd is empty or null, use workspace_roots[0] as fallback
    if [ -z "$cwd" ] || [ "$cwd" == "null" ]; then

fcoury

• Delete unused or obsolete files when your changes make them irrelevant (refactors, feature removals, etc.), and revert files only when the change is yours or explicitly requested. If a git operation leaves you unsure about other agents' in-flight work, stop and coordinate instead of deleting.
• Before attempting to delete a file to resolve a local type/lint failure, stop and ask the user. Other agents are often editing adjacent files; deleting their work to silence an error is never acceptable without explicit approval.
• NEVER edit .env or any environment variable files—only the user may change them.
• Coordinate with other agents before removing their in-progress edits—don't revert or delete work you didn't author unless everyone agrees.
• Moving/renaming and restoring files is allowed.
• ABSOLUTELY NEVER run destructive git operations (e.g., git reset --hard, rm, git checkout/git restore to an older commit) unless the user gives an explicit, written instruction in this conversation. Treat t

fcoury

# Git Worktree Creation Function
function wk --description "Create a git worktree with format <current_dir>-<branch_name>"
    # Check if we're in a git repository
    if not git rev-parse --git-dir >/dev/null 2>&1
        echo "Error: Not in a git repository"
        return 1
    end
    
    set existing_only false
    set branch_name ""

fcoury

function codex_continue
    # Find the most recently modified JSONL file in ~/.codex/sessions (recursively)
    set latest (find ~/.codex/sessions -type f -name '*.jsonl' -print0 2>/dev/null | xargs -0 ls -t 2>/dev/null | head -n 1)

    if test -z "$latest"
        echo "No session files found in ~/.codex/sessions"
        return 1
    end

    echo "Resuming from: $latest"

fcoury

System Prompt

Identity

You are Kiro, an AI assistant and IDE built to assist developers.

When users ask about Kiro, respond with information about yourself in first person.

You are managed by an autonomous process which takes your output, performs the actions you requested, and is supervised by a human user.

You talk like a human, not like a bot. You reflect the user's input style in your responses.

fcoury

=== Full Backtrace ===
#0  0x0000563016f63c87 in v8::internal::MarkingBarrier::MarkValueLocal(v8::internal::Tagged<v8::internal::HeapObject>) () at ../../../../v8/src/heap/marking-barrier-inl.h:98
#1  0x0000563016f633df in void v8::internal::MarkingBarrier::Write<v8::internal::FullHeapObjectSlot>(v8::internal::Tagged<v8::internal::HeapObject>, v8::internal::FullHeapObjectSlot, v8::internal::Tagged<v8::internal::HeapObject>) () at ../../../../v8/src/heap/marking-barrier-inl.h:25
#2  0x000056301720e5f6 in v8::internal::Dictionary<v8::internal::NameDictionary, v8::internal::NameDictionaryShape>::SetEntry(v8::internal::InternalIndex, v8::internal::Tagged<v8::internal::Object>, v8::internal::Tagged<v8::internal::Object>, v8::internal::PropertyDetails) () at ../../../../v8/src/objects/dictionary-inl.h:202
#3  0x000056301720e825 in v8::internal::Handle<v8::internal::NameDictionary> v8::internal::Dictionary<v8::internal::NameDictionary, v8::internal::NameDictionaryShape>::Add<v8::internal::Isolate, (v8::internal::All

fcoury

Here's JavaScript code that will definitely trigger OOM in your deno_core setup:

Memory Bomb - Large Array Allocation

// This will quickly consume memory by creating large arrays
const arrays = [];
let counter = 0;

while (true) {