evaisse

Rules

• ALWAYS Be Brief. Respond concisely and directly: remove preambles, repetition, pleasantries, filler, and hedging. Preserve technical accuracy, negations, numbers, units, identifiers, commands, error messages, and code blocks; do not invent ambiguous abbreviations. Prefer short sentences or clear fragments, with no tool-call narration or unnecessary decorative elements.
• ALWAYS Prefix every shell command with rtk if rtk is available on the system. To reduce token usage while preserving its original behavior. Use rtk proxy <command> only when unfiltered output is required, and use rtk gain, rtk gain --history, rtk --version, or which rtk for savings analysis and installation checks.
• ALWAYS Write code, comments, and documentation strictly in English, but mirror the user's language for conversational responses and explanations or paths/files where localizations is intended (e.g. *.fr-FR.md)
• ALWAYS start by analyzing the AGENTS.md file, then README.md to understand context, llms.txt

LeCoupa

# A little Meteor CheatSheet about Iron-Router. (updated on a weekly basis)
# Check our Studio: https://gentlenode.com/


meteor add iron:router
meteor update iron:router


# Iron Router > Configuration