CUSTOM KNOWLEDGE FEED

#ai

76 cards

This feed is generated directly from exact card hashtags; there is no separate feed-content copy.

Subscribe to this viewRSSJSON

---> Awesome OSINT For Everything A list of osint tools/websites for pentration testing, Reverse Searching, Red team Oprations, information gathering, bugbounty and almost cover everything in single file. Information like metatags, web site records, ISP, virus analysis, open ports, vulnerabilities, subdomains, location, network, WHOIS, DNS records, technologies used, pastes, social media accounts, blacklisted IP, links and other stuff, also you can know if an URL belongs to a

MARKDOWN SNAPSHOT

Loading…

00

MCP Gateway is a reverse proxy and management layer for Model Context Protocol (MCP) servers, enabling scalable, session-aware routing, authorization and lifecycle management of MCP servers in Kubernetes environments. This project provides: Available only when FoundrySettings:Endpoint is configured.

MARKDOWN SNAPSHOT

Loading…

00

Deep Lake: Database for AI Docs • Get Started • API Reference • LangChain & VectorDBs Course • Blog • Whitepaper • Slack • Twitter Deep Lake is a Database for AI powered by a storage format optimized for deep-learning applications. Storing and searching data plus vectors while building LLM applications 2.

MARKDOWN SNAPSHOT

Loading…

00

Awesome AI Regulation, Principles & Guidelines (AKA Writing AI Responsibly) As AI systems become more prevalent in society, we face bigger and tougher societal challenges. Given many of these challenges have not been faced before, practitioners will face scenarios that will require dealing with hard ethical and societal questions.

MARKDOWN SNAPSHOT

Loading…

00

--- name: writing-plans description: Use when you have a spec or requirements for a multi-step task, before touching code --- Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it.

MARKDOWN SNAPSHOT

Loading…

00

NEVER: INSTEAD: Example: your human partner's rule: "External feedback - be skeptical, but check carefully" your human partner's rule: "You and reviewer both report to me. If we don't need this feature, don't add it." Push back when: How to push back: If you're uncomfortable pushing back out loud: Name that tension, then tell your partner about the issue you've seen.

MARKDOWN SNAPSHOT

Loading…

00

Load this reference when: writing or changing tests, adding mocks, or adding cleanup/helper methods for tests. Two principles govern everything here: Strict TDD produces both naturally: a test written first and watched failing against real code has already proven it can fail, and only earns a mock when the real dependency proves slow or external.

MARKDOWN SNAPSHOT

Loading…

00

--- name: finishing-a-development-branch description: Use when implementation is complete, all tests pass, and you need to decide how to integrate the work --- Core principle: Verify tests → Detect environment → Present options → Execute choice → Clean up. Announce at start: "I'm using the finishing-a-development-branch skill to complete this work." Run the project's full test suite (npm test / cargo test / pytest / go test ./...).

MARKDOWN SNAPSHOT

Loading…

00