@ia-ccun/code-agent-cli 0.0.52 → 0.0.54-beta.1

package/config/agent/skills/ponytail-debt/SKILL.md

@@ -0,0 +1,44 @@
+---
+name: ponytail-debt
+description: >
+  Harvest every `ponytail:` comment in the codebase into a debt ledger, so the
+  deliberate shortcuts and deferrals ponytail leaves behind get tracked instead
+  of rotting into "later means never". Use when the user says "ponytail debt",
+  "/ponytail-debt", "what did ponytail defer", "list the shortcuts", "ponytail
+  ledger", or "what did we mark to do later". One-shot report, changes nothing.
+---
+
+Every deliberate ponytail shortcut is marked with a `ponytail:` comment naming
+its ceiling and upgrade path. This collects them into one ledger so a deferral
+can't quietly become permanent.
+
+## Scan
+
+Grep the repo for comment markers, skipping `node_modules`, `.git`, and build
+output:
+
+`grep -rnE '(#|//) ?ponytail:' .`  (add other comment prefixes if your stack uses them)
+
+Each hit is one ledger row. The comment prefix keeps prose that merely mentions
+the convention out of the ledger.
+
+## Output
+
+One row per marker, grouped by file:
+
+`<file>:<line> — <what was simplified>. ceiling: <the limit named>. upgrade: <the trigger to revisit>.`
+
+The convention is `ponytail: <ceiling>, <upgrade path>`, so pull the ceiling
+and the trigger straight from the comment. Want an owner per row too? add
+`git blame -L<line>,<line>`.
+
+Flag the rot risk: any `ponytail:` comment that names no upgrade path or
+trigger gets a `no-trigger` tag, those are the ones that silently rot.
+
+End with `<N> markers, <M> with no trigger.` Nothing found: `No ponytail: debt. Clean ledger.`
+
+## Boundaries
+
+Reads and reports only, changes nothing. To persist it, ask and it writes the
+ledger to a file (e.g. `PONYTAIL-DEBT.md`). One-shot. "stop ponytail-debt" or
+"normal mode" to revert.

package/config/agent/skills/ponytail-help/SKILL.md

@@ -0,0 +1,68 @@
+---
+name: ponytail-help
+description: >
+  Quick-reference card for all ponytail modes, skills, and commands.
+  One-shot display, not a persistent mode. Trigger: /ponytail-help,
+  "ponytail help", "what ponytail commands", "how do I use ponytail".
+---
+
+# Ponytail Help
+
+Display this reference card when invoked. One-shot, do NOT change mode,
+write flag files, or persist anything.
+
+## Levels
+
+| Level | Trigger | What change |
+|-------|---------|-------------|
+| **Lite** | `/ponytail lite` | Build what's asked, name the lazier alternative in one line. |
+| **Full** | `/ponytail` | The ladder enforced: YAGNI → stdlib → native → one line → minimum. Default. |
+| **Ultra** | `/ponytail ultra` | YAGNI extremist. Deletion before addition. Challenges requirements before building. |
+
+Level sticks until changed or session end.
+
+## Skills
+
+| Skill | Trigger | What it does |
+|-------|---------|--------------|
+| **ponytail** | `/ponytail` | Lazy mode itself. Simplest solution that works. |
+| **ponytail-review** | `/ponytail-review` | Over-engineering review: `L42: yagni: factory, one product. Inline.` |
+| **ponytail-help** | `/ponytail-help` | This card. |
+
+Codex uses `@ponytail`, `@ponytail-review`, and `@ponytail-help`; Claude Code
+and OpenCode use the slash-command forms above (OpenCode ships `/ponytail` and
+`/ponytail-review`).
+
+## Deactivate
+
+Say "stop ponytail" or "normal mode". Resume anytime with `/ponytail`.
+`/ponytail off` also works.
+
+## Configure Default Mode
+
+Default mode = `full`, auto-active every session. Change it:
+
+**Environment variable** (highest priority):
+```bash
+export PONYTAIL_DEFAULT_MODE=ultra
+```
+
+**Config file** (`~/.config/ponytail/config.json`, Windows: `%APPDATA%\ponytail\config.json`):
+```json
+{ "defaultMode": "lite" }
+```
+
+Set `"off"` to disable auto-activation on session start, activate manually
+with `/ponytail` when wanted.
+
+Resolution: env var > config file > `full`.
+
+## Update
+
+Enable auto-update once: open `/plugin`, go to Marketplaces, pick ponytail, Enable auto-update. Claude Code then pulls new versions at startup (run `/reload-plugins` when it prompts). Manual refresh: `/plugin marketplace update ponytail` then `/reload-plugins`.
+
+If `/plugin` is not recognized, your Claude Code is out of date. Update it (`npm install -g @anthropic-ai/claude-code@latest`, or `brew upgrade claude-code`) and restart. Other hosts use their own update flow.
+
+## More
+
+Full docs + examples: https://github.com/DietrichGebert/ponytail

package/config/agent/skills/ponytail-review/SKILL.md

@@ -0,0 +1,56 @@
+---
+name: ponytail-review
+description: >
+  Code review focused exclusively on over-engineering. Finds what to delete:
+  reinvented standard library, unneeded dependencies, speculative abstractions,
+  dead flexibility. One line per finding: location, what to cut, what replaces
+  it. Use when the user says "review for over-engineering", "what can we
+  delete", "is this over-engineered", "simplify review", or invokes
+  /ponytail-review. Complements correctness-focused review, this one only
+  hunts complexity.
+---
+
+Review diffs for unnecessary complexity. One line per finding: location, what
+to cut, what replaces it. The diff's best outcome is getting shorter.
+
+## Format
+
+`L<line>: <tag> <what>. <replacement>.`, or `<file>:L<line>: ...` for
+multi-file diffs.
+
+Tags:
+
+- `delete:` dead code, unused flexibility, speculative feature. Replacement: nothing.
+- `stdlib:` hand-rolled thing the standard library ships. Name the function.
+- `native:` dependency or code doing what the platform already does. Name the feature.
+- `yagni:` abstraction with one implementation, config nobody sets, layer with one caller.
+- `shrink:` same logic, fewer lines. Show the shorter form.
+
+## Examples
+
+❌ "This EmailValidator class might be more complex than necessary, have you
+considered whether all these validation rules are needed at this stage?"
+
+✅ `L12-38: stdlib: 27-line validator class. "@" in email, 1 line, real validation is the confirmation mail.`
+
+✅ `L4: native: moment.js imported for one format call. Intl.DateTimeFormat, 0 deps.`
+
+✅ `repo.py:L88: yagni: AbstractRepository with one implementation. Inline it until a second one exists.`
+
+✅ `L52-71: delete: retry wrapper around an idempotent local call. Nothing replaces it.`
+
+✅ `L30-44: shrink: manual loop builds dict. dict(zip(keys, values)), 1 line.`
+
+## Scoring
+
+End with the only metric that matters: `net: -<N> lines possible.`
+
+If there is nothing to cut, say `Lean already. Ship.` and stop.
+
+## Boundaries
+
+Complexity only, correctness bugs, security holes, and performance go to a
+normal review pass, not this one. A single smoke test or `assert`-based
+self-check is the ponytail minimum, not bloat, never flag it for deletion.
+Does not apply the fixes, only lists them.
+"stop ponytail-review" or "normal mode": revert to verbose review style.

package/config/agent/skills_bak/milvus-skill/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/config/agent/skills_bak/milvus-skill/README.md

@@ -0,0 +1,37 @@
+# milvus-skill
+
+An agent skill that teaches LLMs how to use [pymilvus](https://github.com/milvus-io/pymilvus) to operate [Milvus](https://milvus.io/) vector database.
+
+## What's Included
+
+- **SKILL.md** — Main skill definition with connection, collection management, vector operations, and index management
+- **references/** — Detailed reference docs for each feature area:
+  - `collection.md` — Data types, schema fields, collection operations
+  - `vector.md` — Insert, search, hybrid search, full-text search, iterators, filters
+  - `index.md` — Index types, metric types, create/manage indexes
+  - `partition.md` — Partition CRUD
+  - `database.md` — Database management
+  - `user-role.md` — RBAC: users, roles, privileges
+  - `patterns.md` — Common patterns (RAG, semantic search, hybrid search, full-text search)
+
+## Install as Claude Code Skill
+
+```bash
+claude skill add --url https://github.com/zilliztech/milvus-skill
+```
+
+## Capabilities
+
+- Connect to Milvus Lite, Standalone, Cluster, or Zilliz Cloud
+- Create collections with quick or custom schemas
+- Insert, upsert, search, query, get, delete vectors
+- Hybrid search with RRF/Weighted reranking
+- Full-text search with BM25
+- Paginated iteration over large result sets
+- Index management (AUTOINDEX, HNSW, IVF_FLAT, etc.)
+- Partition, database, and RBAC management
+
+## Requirements
+
+- Python 3.8+
+- `pymilvus` (`pip install pymilvus`)

package/config/agent/skills_bak/milvus-skill/SKILL.md

@@ -0,0 +1,259 @@
+---
+name: milvus-skill
+description: Operate Milvus vector database with pymilvus Python SDK. Use when the user wants to connect to Milvus, create collections, insert vectors, perform similarity search, hybrid search, full-text search, manage indexes, partitions, databases, or RBAC via Python code.
+license: Apache-2.0
+compatibility: Requires Python 3.8+ and pymilvus (pip install pymilvus). Runs on macOS and Linux.
+metadata:
+  author: zilliztech
+  version: "1.0.0"
+allowed-tools: Bash Read Write
+---
+
+# Milvus Vector Database Skill
+
+Operate [Milvus](https://milvus.io/) vector databases directly through Python code using the `pymilvus` SDK. Covers the full lifecycle — connecting, schema design, collection management, vector CRUD, search, hybrid search, full-text search, indexing, partitions, databases, and RBAC.
+
+## When to Use
+
+Use this skill when the user wants to:
+- Connect to a Milvus instance (local, standalone, cluster, or Milvus Lite)
+- Create collections with custom schemas
+- Insert, upsert, search, query, get, or delete vectors
+- Perform hybrid search with reranking
+- Perform full-text search (BM25)
+- Manage indexes, partitions, databases
+- Set up users, roles, and access control (RBAC)
+- Build RAG pipelines, semantic search, or recommendation systems with Milvus
+- Iterate over large result sets with search/query iterators
+
+## Requirements
+
+- Python 3.8+
+- `pymilvus` (`pip install pymilvus`)
+- A running Milvus instance, or use Milvus Lite (embedded, file-based) for development
+
+## Capabilities Overview
+
+| Area | What You Can Do |
+|------|----------------|
+| **Connection** | Connect to Milvus Lite, Standalone, Cluster, or Zilliz Cloud |
+| **Collections** | Create (quick or custom schema), list, describe, drop, rename, truncate, load, release |
+| **Vectors** | Insert, upsert, search, hybrid search, query, get, delete |
+| **Full-Text Search** | BM25-based keyword search with sparse vectors |
+| **Iterators** | Paginated search and query over large datasets |
+| **Indexes** | Create (AUTOINDEX, HNSW, IVF_FLAT, etc.), list, describe, drop |
+| **Partitions** | Create, list, load, release, drop |
+| **Databases** | Create, list, switch, drop |
+| **RBAC** | Users, roles, privileges management |
+
+---
+
+## Connection
+
+> **IMPORTANT: Before writing any connection code, you MUST ask the user for their connection details.** Ask:
+> 1. **Deployment type** — Milvus Lite (local file), Standalone/Cluster (self-hosted), or Zilliz Cloud (managed)?
+> 2. **URI** — For self-hosted: host and port (e.g., `http://localhost:19530`). For Zilliz Cloud: the endpoint URL.
+> 3. **Authentication** — Token, API key, or username/password if required.
+> 4. **Database name** — If not using the default database.
+>
+> **Never assume or hardcode connection parameters.** Use Milvus Lite (`uri="./milvus.db"`) only if the user explicitly wants local/embedded mode for development.
+
+```python
+from pymilvus import MilvusClient
+
+# Milvus Lite (embedded, file-based — great for dev/test)
+client = MilvusClient(uri="./milvus.db")
+
+# Standalone / Cluster Milvus (ask user for actual host:port and credentials)
+client = MilvusClient(uri="<USER_URI>", token="<USER_TOKEN>")
+
+# Zilliz Cloud (ask user for endpoint and API key)
+client = MilvusClient(uri="<USER_ZILLIZ_ENDPOINT>", token="<USER_API_KEY>")
+```
+
+**Parameters:**
+
+| Parameter | Type | Description |
+|-----------|------|-------------|
+| `uri` | str | `"./file.db"` for Milvus Lite, `"http://host:19530"` for server |
+| `token` | str | API key or `"username:password"` |
+| `user` | str | Username (alternative to token) |
+| `password` | str | Password (alternative to token) |
+| `db_name` | str | Target database (default: `"default"`) |
+| `timeout` | float | Operation timeout in seconds |
+
+### Async Client
+
+```python
+from pymilvus import AsyncMilvusClient
+
+async with AsyncMilvusClient(uri="<USER_URI>") as client:
+    results = await client.search(collection_name="my_collection", data=[query_vector], limit=10)
+```
+
+---
+
+## Collection Management
+
+### Quick Create (auto schema + auto index + auto load)
+
+```python
+client.create_collection(
+    collection_name="my_collection",
+    dimension=768,
+    metric_type="COSINE"  # Optional: "COSINE" (default), "L2", "IP"
+)
+```
+
+This automatically creates an `id` field (INT64, primary key, auto_id), a `vector` field (FLOAT_VECTOR), AUTOINDEX, and auto-loads the collection.
+
+### Custom Schema Create
+
+```python
+from pymilvus import DataType
+
+schema = client.create_schema(auto_id=False, enable_dynamic_field=True)
+schema.add_field("id", DataType.INT64, is_primary=True)
+schema.add_field("text", DataType.VARCHAR, max_length=512)
+schema.add_field("embedding", DataType.FLOAT_VECTOR, dim=768)
+
+index_params = client.prepare_index_params()
+index_params.add_index(field_name="embedding", index_type="AUTOINDEX", metric_type="COSINE")
+
+client.create_collection(collection_name="my_collection", schema=schema, index_params=index_params)
+```
+
+**See [references/collection.md](references/collection.md) for data types, add_field parameters, and all collection operations.**
+
+### Other Collection Operations
+
+```python
+client.list_collections()
+client.describe_collection(collection_name="my_collection")
+client.has_collection(collection_name="my_collection")
+client.rename_collection(old_name="old", new_name="new")
+client.drop_collection(collection_name="my_collection")
+client.truncate_collection(collection_name="my_collection")
+client.load_collection(collection_name="my_collection")
+client.release_collection(collection_name="my_collection")
+client.get_load_state(collection_name="my_collection")
+client.get_collection_stats(collection_name="my_collection")
+```
+
+- Quick create is best for prototyping; use custom schema for production.
+- A collection must be **loaded** before search or query.
+- Use `enable_dynamic_field=True` to allow inserting fields not defined in the schema.
+
+---
+
+## Vector Operations
+
+**See [references/vector.md](references/vector.md) for hybrid search, full-text search, iterators, filter syntax, and detailed examples.**
+
+### Insert / Upsert
+
+```python
+# Vectors must come from an embedding model — never use fake/placeholder vectors
+from pymilvus import model
+
+embedding_fn = model.dense.SentenceTransformerEmbeddingFunction(model_name="all-MiniLM-L6-v2")
+
+docs = ["AI advances in 2024", "ML basics for beginners"]
+vectors = embedding_fn.encode_documents(docs)
+
+data = [
+    {"id": 1, "text": docs[0], "embedding": vectors[0]},
+    {"id": 2, "text": docs[1], "embedding": vectors[1]},
+]
+client.insert(collection_name="my_collection", data=data)
+client.upsert(collection_name="my_collection", data=data)
+```
+
+### Search (vector similarity)
+
+```python
+# Use the same embedding model to encode the query
+query_vectors = embedding_fn.encode_queries(["What is artificial intelligence?"])
+
+results = client.search(
+    collection_name="my_collection",
+    data=query_vectors,
+    anns_field="embedding",
+    limit=10,
+    output_fields=["text", "id"],
+    filter='age > 20 and status == "active"',
+    search_params={"metric_type": "COSINE", "params": {"nprobe": 10}}
+)
+```
+
+### Query / Get / Delete
+
+```python
+# Query by filter
+client.query(collection_name="my_collection", filter='id in [1, 2, 3]', output_fields=["text"], limit=100)
+
+# Get by primary key
+client.get(collection_name="my_collection", ids=[1, 2, 3], output_fields=["text"])
+
+# Delete
+client.delete(collection_name="my_collection", ids=[1, 2, 3])
+client.delete(collection_name="my_collection", filter='status == "obsolete"')
+```
+
+- **Never use fake or placeholder vectors** (e.g., `[0.1, 0.2, ...]`). Always generate vectors from an embedding model.
+- Use `pip install "pymilvus[model]"` for built-in embedding functions, or use any embedding model (OpenAI, Cohere, etc.).
+- Vector dimension in search must match the collection schema exactly.
+- The query embedding model must be the **same model** used to generate the stored vectors.
+- For large inserts, batch data into chunks (e.g., 1000 rows per batch).
+- For large result sets, use iterators — see [references/vector.md](references/vector.md).
+
+---
+
+## Index Management
+
+**See [references/index.md](references/index.md) for index types, metric types, and parameters.**
+
+```python
+index_params = client.prepare_index_params()
+index_params.add_index(
+    field_name="embedding",
+    index_type="HNSW",
+    metric_type="COSINE",
+    params={"M": 16, "efConstruction": 256}
+)
+client.create_index(collection_name="my_collection", index_params=index_params)
+
+client.list_indexes(collection_name="my_collection")
+client.describe_index(collection_name="my_collection", index_name="my_index")
+client.drop_index(collection_name="my_collection", index_name="my_index")
+```
+
+- `AUTOINDEX` is recommended for most use cases.
+- An index is required before loading a collection.
+
+---
+
+## Additional Features
+
+| Feature | Reference |
+|---------|-----------|
+| Partition Management | [references/partition.md](references/partition.md) |
+| Database Management | [references/database.md](references/database.md) |
+| User & Role Management (RBAC) | [references/user-role.md](references/user-role.md) |
+| Common Patterns (RAG, Semantic Search) | [references/patterns.md](references/patterns.md) |
+
+---
+
+## General Guidance
+
+- **Always ask the user for connection details** (URI, token/credentials) before writing connection code. Never assume or hardcode connection parameters.
+- **Never generate fake or placeholder vectors.** Always use an embedding model to produce real vectors. Suggest `pip install "pymilvus[model]"` for built-in embedding functions.
+- For quick prototyping, use **Milvus Lite** (`uri="./file.db"`) — no server needed, but only if the user explicitly requests local/embedded mode.
+- A collection must be **loaded into memory** before search/query.
+- The vector dimension in search data must **exactly match** the collection schema.
+- The query embedding model must be the **same model** used to generate the stored vectors.
+- Before any destructive operation (drop collection, drop database, delete vectors), always confirm with the user.
+- Use `enable_dynamic_field=True` when the schema may evolve.
+- Prefer `AUTOINDEX` unless the user has specific performance requirements.
+- Use `truncate_collection` to clear all data without dropping the collection.
+- For large datasets, use iterators (`search_iterator`, `query_iterator`) instead of increasing limit.