Results for “business-data”

8 skills
More results
antigravity
Hasdata
Extract public web data, search engine results, and structured data from platforms like Google, Amazon, and Zillow using HasData APIs.
42.4k · bundle
antigravity
Hasdata CLI
Provides command-line access to search, scraping, and structured web data from over 40 APIs including Google, Amazon, Yelp, and Zillow.
42.4k · bundle
theheavenlyd3mon
Clean Architecture
Structure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters", "hexagonal architecture", "use case boundary", "onion architecture", "screaming architecture", or "framework independence". Also trigger when decoupling business logic from databases or frameworks, defining module boundaries, or debating where to put business rules. Covers component principles, boundaries, and SOLID. For code quality, see clean-code. For domain modeling, see domain-driven-design.
28 · bundle
wondelai
Clean Architecture
Structure software around the Dependency Rule so that source code dependencies point inward from frameworks to use cases to entities, keeping business rules independent of databases, UI, and external agencies.
1.6k · bundle
shulkwisec
Threat Modeling
Structured threat modeling skill using the PASTA framework (Process for Attack Simulation and Threat Analysis) combined with Adam Shostack's 4-question framework. Use this skill whenever the user asks to do threat modeling, security analysis, map the attack surface, identify threats, or review an application for security risks — even if they don't mention PASTA or a specific framework by name. Core activities: Component Mapping (architecture + data flows), Critical Assessment (business impact prioritization), and Logic Flaw Identification (attacker mindset on business logic). Produces: component map diagram (Mermaid), data flow diagram (Mermaid), attack tree (Mermaid), STRIDE threat table, prioritized risk register, and an actionable mitigation plan. Invoke proactively for any security review, architecture review, or "what could go wrong?" session.
21