Based in Brazil
// 4 min

AI Context Checklist: From Chatting to Architecting

AI Engineering Productivity

The Goal: Stop correcting the AI. Start directing it.

1. The “Plan-First” Protocol

Stop the “Review Trap” by forcing the AI to think before it types.

  • The Rule: Never ask for code immediately for a new feature.
  • The Prompt: “I want to implement [Feature]. Do not write any code yet. Review the codebase and list the files you need to modify and the logic steps you will take. Wait for my ‘Go’ before writing code.”
  • Why it works: You catch architectural bugs in 10 seconds of reading a list, rather than 5 minutes of debugging a 100-line file.

2. Context is King (The Command Palette)

AI logic is only as good as the files it can “see.”

  • @workspace / #codebase: Use for “Where is…?” or “How do we handle…?” questions.
  • @file / #file: Use this religiously. Point to your specific Service, View, or Model.
  • @terminal / @logs: If an app crashes, don’t describe the error. Paste the raw log/terminal output and ask: “Explain why this occurred based on the logic in @file.”

3. Mobile & Fullstack Specifics

Bridging the gap between iOS and Web.

  • The Xcode Gap: Since Xcode integration can be less “context-aware” than VS Code, manually reference your Protocols and Models.
  • Cross-Stack Sync: When changing an API, mention both sides: “Update UserAPI.swift to match the schema changes I just made in user_controller.ts.”
  • The “Internal” Pattern: If your team uses a specific pattern (e.g., MVVM, Composable Architecture), tell the AI: “Follow the pattern used in ExistingView.swift exactly.”

4. The 4-Part Prompt Formula

Use this for complex tasks to ensure high-quality output.

  1. Role: “Act as a Senior iOS & Fullstack Engineer.”
  2. Context: “We are working on the [Project Name] using existing_pattern.swift.”
  3. Task: “Implement the logic for [X] feature.”
  4. Constraints: “Use async/await, do not add external dependencies, and follow the naming conventions in styleguide.md.”

5. Setting “Project Rules” (The Guardrails)

Standardize the AI for the whole team.

  • Create a .github/copilot-instructions.md (for Copilot) or a .cursorrules file in your root.
  • Include:
    • “Always use SwiftUI, never UIKit.”
    • “Use our Logger.swift for all error handling.”
    • “Prefer functional programming patterns in TypeScript.”
    • “If a function exceeds 25 lines, suggest a refactor.”
← Back to blog