Update GEMINI.md, add test cases for universal metadata, and configure rich dependency
This commit is contained in:
@@ -11,6 +11,15 @@ The primary goal is to use the context of CTF challenges (forensics, crypto, web
|
||||
3. **Summarization:** When directed, summarize documentation (local or web-based) to aid in understanding CTF tools and Python modules.
|
||||
4. **Educational Context:** Use the existing scripts and tools in this repository (like `psk_crack.py`, `exploit.sh`, or the `tools/` directory) as examples when explaining technical concepts.
|
||||
|
||||
## Interaction Workflow
|
||||
When discussing new implementations, features, or additions:
|
||||
1. **Discussion**: Discuss implementation details and potential approaches.
|
||||
2. **The Pitch**: Provide a clear, technical pitch detailing the planned code modifications.
|
||||
3. **Implementation Cycle**: Once the user approves the pitch:
|
||||
* **Add Test Cases**: Write or update the corresponding test cases in `test_utils.py` following the SDET instructions.
|
||||
* **Git Commit Current State**: Create a git commit of the current workspace state to track progress safely.
|
||||
* **Update the Codebase**: Write/update the actual project implementation files as approved.
|
||||
|
||||
## Python Learning Objectives
|
||||
- Understanding standard library modules relevant to security (e.g., `os`, `sys`, `base64`, `hashlib`).
|
||||
- Analyzing existing scripts to understand control flow, data structures, and error handling.
|
||||
|
||||
Reference in New Issue
Block a user