defense-prep
Skill0 starsChanged 21 days agoMITView on GitHub
毕业设计答辩准备（答辩 PPT 提纲、讲稿与时间分配、演示脚本、老师常问问题及回答思路）。准备答辩、做答辩 PPT、模拟答辩提问时使用。
1 other project uses a version of this.
Adopted by
Most recently taken up by
- kinhluan/skillstheir own version, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- kinhluan/skills★ 6same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- code-to-thesisSkill
- requirements-analysisSkill
- system-designSkill
- test-chapterSkill
- thesis-proposalSkill
- thesis-writingSkill
The file
Files
答辩准备
PPT 提纲（一般 12–18 页，讲 8–10 分钟，以学院要求为准）
- 封面（题目、姓名、学号、指导老师）
- 选题背景与意义（1 页，一个真实痛点）
- 研究内容 / 主要工作（1 页）
- 技术选型与系统架构（1–2 页，放架构图）
- 功能模块图（1 页）
- 数据库设计（1 页，E-R 图，不要放整张表格）
- 核心功能与实现（3–5 页，每页一个功能：截图 + 一句话 + 关键点）
- 难点与解决（1–2 页，最能体现个人能力）
- 系统测试（1 页，用例数、发现并修复的问题）
- 总结与不足、展望（1 页）
- 致谢
原则：一页一个观点，字少图多，字号不小于 18；截图来自真实系统。
讲稿
按页写口语化讲稿，标注每页用时，总时长控制在要求内。演示环节写演示脚本：先登录哪个账号 → 展示哪 3 个功能 → 准备好测试数据；提前录好演示视频以防现场环境出问题。
常见提问（帮用户准备基于其系统的真实回答，不要替用户编经历）
- 这个系统和现有的 xx 平台有什么区别？创新点在哪？
- 为什么选这个技术栈？前后端怎么通信、怎么做的登录鉴权？
- 数据库为什么这样设计？这两张表是什么关系？
- 密码怎么存的？怎么防止越权 / SQL 注入？
- 某个功能的实现流程（让你现场讲代码）
- 测试是怎么做的？发现过什么 bug？
- 系统有什么不足？如果继续做会怎么改？
- 哪些部分是自己写的、用了哪些开源组件或 AI 工具？——如实回答，符合学校规定。
模拟答辩
用户要求时，扮演答辩老师，基于论文和代码每次提一个问题，用户回答后点评（准确性、是否答到点上），最后汇总薄弱点。
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.