APromptAura

#architecture

Top prompts tagged architecture.

0
p/imagegenAauraNovice4 days agohas example○Not yet verified

Brutalist architecture photo with dramatic weather and scale

Brutalist concrete building, building_type, photographed from a low wide angle to emphasize monumental scale, dramatic overcast sky with heavy storm clouds rolling in, single tiny human figure included for scale reference near the entrance, harsh raking light picking out the texture of board-formed concrete, symmetrical or strongly geometric composition, shot on a 24mm tilt-shift lens to keep verticals perfectly straight, muted desaturated color palette of grey, ochre and slate blue, architectural photography style similar to Hélène Binet, high dynamic range with deep shadow detail --ar 16:9 --style raw --v 6 Negative prompt: no people crowding the frame, no cars, no signage, no lens distortion, no converging verticals, no color grading toward warm tones, no blur
Midjourney#architecture#brutalism#weather
0
0
p/agentsAauraNovice4 days agohas example⁂auto-checked

Design a two-tier memory architecture for a long-running assistant agent

Design a memory system for an agent that runs {{deployment_context, e.g. a persistent assistant across many sessions with the same user}}. I need a concrete design, not general advice. Cover: 1. What goes in short-term (working/session) memory versus long-term (persisted) memory, with specific examples relevant to this agent's task, and the rule for when something graduates from one to the other. 2. Write format for long-term memories: structured fields (not raw transcript dumps) so they're retrievable and don't bloat the context window, give me the actual schema. 3. Retrieval strategy: how the agent decides what to pull into context for a given turn (recency, relevance search, explicit user reference), and how to avoid retrieving stale or contradicted memories. 4. Conflict resolution: what happens when a new fact contradicts a stored memory (e.g. user says their preference changed) - should it overwrite, version, or flag for confirmation. 5. A concrete forgetting/pruning policy so memory doesn't grow unbounded, with a specific trigger (age, low retrieval frequency, explicit user request) rather than 'periodically clean up'. Agent context: deployment_context Expected memory volume/session frequency: volume_context
ClaudeGPT#memory#agent-design#architecture
0
0
p/codingAauraNovice4 days agohas example⁂auto-checked

Architecture Decision Record generator that surfaces the real tradeoffs

Write an Architecture Decision Record (ADR) for the decision: decision_summary. Use this structure and hold yourself to it strictly: 1. Context: what problem forced this decision, including constraints (team size, timeline, existing stack) that ruled out otherwise-reasonable options. Be concrete, not generic. 2. Options considered: at least 2 real alternatives besides the chosen one, each with the honest case FOR it, not a strawman. If an option was rejected mainly for a non-technical reason (team familiarity, timeline), say that plainly instead of inventing a technical excuse. 3. Decision: what was chosen, one paragraph. 4. Consequences: both the benefits AND the costs/risks this decision introduces, explicitly labeled, don't bury the downsides in a single soft sentence. 5. Revisit trigger: a concrete condition under which this decision should be reconsidered (e.g. 'if write volume exceeds X/sec' or 'if team grows past Y engineers'), not 'if it stops working'. Decision details, options I actually considered, and constraints: details
ClaudeGPT#architecture#documentation#decision-making
0
0
p/codingAauraNovice4 days agohas example⁂auto-checked

Plan a legacy framework migration with a reversible, staged rollout

I need to migrate codebase_description from old_framework to new_framework. Produce a migration plan, not code, structured as: 1. Inventory: what categories of code/config depend on the old framework's specific behavior (not just imports, actual behavioral coupling like implicit type coercion, routing conventions, middleware order). 2. Strangler-fig staging: an order of migration that lets old and new run side by side, with the riskiest, most-coupled piece migrated last, not first. 3. For each stage, a concrete rollback trigger (a metric or error class, not 'if it feels wrong') and how to revert that stage specifically without reverting the whole migration. 4. Testing strategy per stage: what must have parity tests before cutover versus what can be verified by monitoring after. 5. A list of behavioral differences between old_framework and new_framework that commonly cause silent bugs during this exact migration, so I know what to watch for. Do not recommend a big-bang rewrite unless you can justify why staging is not possible here.
ClaudeGPT#migration#architecture#rollout-strategy
0