Information on Current Plans:

I've successfully completed many tasks I previously set. Currently, I've fully redesigned the Blueprint to better suit my specific needs.

The Blueprint has been made non-interactive, and additional configurations with event subscriptions have been introduced (e.g., prehook).

"scripts": {
  "bp": "blueprint",
  "prebuild": "npx @ton-ai-core/blueprint-linter",
  "postbuild": "blueprint misti",
  "build": "blueprint build",
  "prerun:deploy\\w+": "blueprint generate-specs && blueprint test",
  "prerun:\\w+": "blueprint generate-specs && blueprint test ./tests/$BLUEPRINT_SCRIPT_NAME.spec.ts",
  "start": "blueprint run",
  "pretest": "npx blueprint build --all && eslint . --ext .ts",
  "test": "jest --verbose",
  "lint": "eslint . --ext .ts",
  "misti": "blueprint misti"
}

I've created a simple linter for Blueprint (https://github.com/ton-ai-core/blueprint-linter) which checks the correctness of contract file names and directory structures.

Additionally, I've implemented automated test generation for scripts in the script folder (https://github.com/ton-ai-core/blueprint-sandbox). This generates nearly functional tests automatically for scripts to ensure each script is tested locally before deployment to the blockchain, significantly reducing issues when working with AI.

Work continues on the https://github.com/ton-ai-core/contract-knowlenge project. Although my customized version with additional insights isn't ready yet, I plan to release it shortly.

Upcoming Plans:

1. Develop a Telegram user bot to run on GitHub Actions (scheduled every 6 hours). This bot will parse Telegram channels related to TON (e.g., https://t.me/tactlang, https://t.me/tondev_eng). Data collected from these channels will serve as a dataset for AI in the contract-knowledge project.

2. Ensure the prompt system updates automatically when any command is executed. There will be a dedicated .mdc file continuously updated via a special command, which will generate the subproject structure for contract-knowledge. For example:

### SbtProject `projects/SbtProject`
- **contracts/** (1 file)
  - `contracts/Proposal.tact`
- **script/** (1 file)
  - `script/deployProposal.ts`
- **wrappers/** (2 files)
  - `wrappers/Proposal.ts`
  - `wrappers/Proposal.compile.ts`
- **tests/** (2 files)
  - `tests/proposal.spec.ts`
  - `tests/public1.spec.ts`

### TonVoting `projects/TonVoting`

This approach will help AI recognize existing working projects. I'll also experiment with chat functionality to allow AI to reference recent conversation history, further enhancing context understanding.

3. Introduce a new Blueprint plugin focused on contract formatting. For Tact contracts, for instance, the command npx tact-fmt -w ./contracts will be utilized.

4. Refactor and reorganize all documentation stored at https://github.com/ton-ai-core/contract-knowlenge/tree/main/.knowlenge. The recent update in Cursor allows the agent to view all project folders. To leverage this effectively, a thorough cleanup and documentation restructuring is essential.

5. Continue refining prompts for .mdc and .cursorrules files.