thethreemagi/IYmtg
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Updated code

Browse Source
This commit is contained in:
Mike Wichers
2026-03-05 20:27:35 -05:00
parent 13753359b3
commit 8b57eeb108
3 changed files with 225 additions and 30 deletions
Download Patch File Download Diff File Expand all files Collapse all files

64
ai_blueprint.md
View File

@@ -1,41 +1,45 @@
# AI Blueprint
# AI Blueprint: Full Project Readiness Audit
This document outlines the architecture and plan for development tasks. It is intended to be used by the development team to guide implementation.
## Goal
## Instructions for the Architect AI
To perform a comprehensive audit of the `IYmtg_App_iOS` project to ensure it can be compiled without errors and to identify any missing or incomplete features before handing it off to a human developer.
1. **Understand the Goal:** Your primary role is to understand the user's request and create a detailed, step-by-step plan for another AI (Claude) to execute. You do not write code.
2. **Analyze the codebase:** Use the available tools to explore the existing files and understand the current state of the project.
3. **Create a Plan:** Based on the user's request and your analysis, create a comprehensive plan. This plan should be broken down into clear, actionable steps. Each step should include:
* A description of the task.
* The specific files to be modified.
* The high-level changes required.
4. **Update this Blueprint:** Overwrite this `ai_blueprint.md` file with the generated plan.
5. **Include README and Commit Steps:** The plan must always include steps for:
* Updating the `README.md` if the changes affect the project's description, setup, or usage.
* Creating a Git commit with a descriptive message to save the changes.
6. **Delegate Implementation:** After creating the plan, your job is complete. Another AI will take over to implement the plan.
## Audit Steps for Claude
## Development Plan
1. **Dependency Verification:**
* Review the project's dependencies. Since this is a Swift project, check for any package manager configurations (like Swift Package Manager, CocoaPods, or Carthage). If any are found, ensure all required dependencies are listed and correctly configured.
* Verify that all required versions of dependencies are compatible with the project's Swift version.
> **Note to the Architect AI:** Replace this section with the actual plan for the user's request.
2. **File and Resource Integrity Check:**
* Scan the project for any missing files or broken links. Pay close attention to assets, storyboards, and any other resources referenced in the code.
* Ensure all necessary `.swift` files are included in the build targets.
### 1. Analyze Existing Code
3. **Static Code Analysis:**
* Perform a static analysis of the entire Swift codebase in `IYmtg_App_iOS/`.
* Look for common compilation issues such as:
* Syntax errors.
* Type mismatches.
* Unresolved identifiers (e.g., variables or functions that are used but not defined).
* Incorrect use of optionals.
* API deprecation warnings.
- **File:** `[Path to relevant file]`
- **Description:** Briefly describe the purpose of the file and the area to be modified.
4. **Feature Completeness Review:**
* Examine the code for any features that are stubbed out, marked with `// TODO:`, `// FIXME:`, or are otherwise incomplete.
* Pay special attention to the `Features` directory (`IYmtg_App_iOS/Features/`) to assess the state of each feature (CardDetail, Collection, Help, Scanner).
* Check for any disabled or commented-out code that might indicate an incomplete feature.
### 2. Implement Changes
5. **Audit Summary Report:**
* Create a summary of all findings in a new file named `claude_review_summary.md`.
* For each issue, provide a description, the file path, and the relevant line number(s).
* Categorize the issues by severity (e.g., Blocker, Critical, Major, Minor).
- **File:** `[Path to file to be created or modified]`
- **Description:** Detail the changes to be made. For new files, describe the file's purpose and structure.
6. **Update README.md:**
* Add a new section to the `README.md` file titled "Project Audit".
* Under this section, add a brief summary of the audit's outcome and a link to the `claude_review_summary.md` file.
### 3. Update Documentation
7. **Create Git Commit:**
* Stage all the changes (the new `claude_review_summary.md` and the updated `README.md`).
* Create a Git commit with the message: "feat: Complete project readiness audit".
- **File:** [`README.md`](README.md)
- **Description:** Update the README to reflect the new changes, features, or bug fixes.
### 4. Commit Changes
- **Action:** Create a Git commit.
- **Commit Message:** `feat: [A brief, descriptive message of the changes]`
8. **Increment Project Version:**
* If the audit reveals significant issues that require code changes, increment the project's build number. If no significant issues are found, this step can be skipped. The location of the version number is likely in the project's settings or an `Info.plist` file.