← Prompt Library / Engineering
Set up sane feature-flag practice: naming, lifespan rules, the kill-switch discipline, and the cleanup ritual that prevents flag graveyards.
Set up feature-flag discipline for {{team}} (stack, current flag usage/mess: {{current}}). Define: flag types with different rules (release flags — short-lived, weeks; ops/kill-switches — permanent, documented; experiment flags — until significance), naming convention (type prefix + feature + ticket), the lifespan rule (every release flag gets a removal ticket CREATED WITH the flag — flags without expiry become permanent config nobody understands), the default-state and failure-mode rule (what happens if the flag service is down), testing both states honestly, and the monthly flag review: the list, each one justified or scheduled for deletion.
Fields like {{ this }} are placeholders — replace them with your own details, or let Aria ask you for them.
This prompt runs with Aria connected to your email, files, CRM and 40+ other services — and you can schedule it to run automatically.
Start Free WeekReview a diff for correctness, security, and readability issues.
Get a plain-English walkthrough of unfamiliar code.
Generate thorough unit tests for a function.
Diagnose an error systematically: likely causes ranked with reasoning, the cheapest test for each, a...
Build a regular expression from a plain-English requirement — explained token by token, tested again...
Turn a plain-English data question into a working SQL query — with the assumptions stated, a readabl...