summarize-as-experience

Consolidate AngelScript conversation context into .cursor rules and skill knowledge.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/moraluco/Illusion-Cursor-dev-kit --skill summarize-as-experience
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: summarize-as-experience
Source: https://github.com/moraluco/Illusion-Cursor-dev-kit/tree/main/.cursor/skills/summarize-as-experience
Command: npx skills add https://github.com/moraluco/Illusion-Cursor-dev-kit --skill summarize-as-experience

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill captures ad-hoc AngelScript decisions and project conversation context and turns them into persistent, discoverable rules and knowledge so the write-angelscript skill and Kit content remain the single authoritative source for AS practices.

Core Features & Use Cases

  • Extract knowledge points from the current conversation, existing rules, and Kit content to produce reusable AS conventions.
  • Design and update .mdc rules under .cursor/rules to encode checks, globs, and alwaysApply directives.
  • Consolidate findings into write-angelscript by updating its SKILL.md and reference/gotchas sections so future agents use the updated guidance.
  • Optional knowledgebase updates to content/knowledge or content/dev when new documentation, indexes, or gotchas are warranted.
  • Audit-friendly reporting that lists which rules or skill sections were added or changed and points to their paths.

Quick Start

Summarize the AngelScript decisions from this conversation, update .cursor/rules entries as needed, and merge all findings into .cursor/skills/write-angelscript and content/knowledge.

Frequently Asked Questions about summarize-as-experience

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I save AngelScript coding conventions from a conversation into persistent rules?

You consolidate AngelScript development conversations by extracting coding conventions and API usage, then proposing or editing .mdc rule files under .cursor/rules to make those decisions persistent and discoverable.

What is the best way to maintain knowledge artifacts for Unreal Engine AngelScript projects?

The best way to maintain AngelScript knowledge artifacts is to consolidate project context and conversation decisions into write-angelscript skill files and the content/knowledge directory, keeping project code roots untouched.

Can I automatically update .cursor rules from Unreal Engine AngelScript chat context?

Yes, you can automatically update .cursor rules by extracting knowledge points from AngelScript chat context and applying them to design or edit .mdc rule files with appropriate globs and alwaysApply directives.

Does this approach modify the actual project code roots when extracting AngelScript API usage?

No, extracting AngelScript API usage and generating rules strictly avoids changes to project code roots. It only modifies .cursor/rules, .cursor/skills/write-angelscript, and content/knowledge directories to ensure project code remains untouched.

How do I consolidate gotchas and API usage into the write-angelscript skill?

You consolidate AngelScript API usage and gotchas by merging findings into the write-angelscript skill, specifically updating its SKILL.md and reference sections so future agents apply the updated guidance during development.

When do I need to generate knowledgebase documentation for AngelScript development decisions?

You generate knowledgebase documentation when new indexes, gotchas, or general documentation are warranted during AngelScript conversation consolidation, updating content/knowledge or content/dev to maintain a comprehensive reference alongside the rules.