9 results for “documents”
Upload files or raw text into a Senso knowledge base. Handles file upload via presigned URLs, raw text/markdown creation, folder targeting, and processing status polling. Use when the user wants to add documents, files, or text content to their Senso KB.
Ingest documents into your Senso.ai knowledge base through Edith smart glasses. Triggers when user wants to add content to their knowledge base.
Search a Senso knowledge base for verified answers, context chunks, or content IDs. Use when the user asks a question that should be grounded in organizational knowledge, says "check Senso", or needs factual answers backed by verified documents.
Setup for Senso's Shared Context path. It writes Start Here, the first document every agent on the team reads, at the root of the knowledge base. The user describes the organization, or the agent writes it from a project folder, a file, or the organization's own documents. Use when senso-shared-context sends the user here because the knowledge base is empty or has no Start Here, or when the user says "set up Shared Context" or "write our Start Here". Do not use for the Verification Loop setup (senso-verification-loop-setup). Do not use when the user names material to save (senso-context-layer).
Audit all environment variable usage in the codebase and generate a complete, documented .env.example. Use when the user says "what env vars do I need?", "document the config", "set up .env.example", or when onboarding someone new to the project.
Search your Senso.ai knowledge base hands-free through Edith smart glasses. Triggers on knowledge/document queries.
Write an enthusiastic, well-structured PR description for the current changes. Use when the user is about to open a pull request and says "write a PR description", "describe these changes", or "hype up this PR".
Explain a piece of code, concept, or system in plain English with zero assumed knowledge. Use when the user is confused, new to a codebase, or says "I have no idea what this does", "explain this to me", or "ELI5".
Generate a structured mental model of an unfamiliar codebase — entry points, data flow, key abstractions, and gotchas. Use when starting on a new repo, when the user says "explain this codebase", "how does this work", "onboard me", or before making large changes to unfamiliar code.